How to sign APK on Android Studio even with non-translated strings?

AndroidAndroid StudioApkTranslation

Android Problem Overview


Background

I've recently migrated my app to Android-Studio. I had some issues doing so, but I got over them eventually.

The problem

For some reason, on Android Studio, when I try to sign an APK, I get a lot of errors that look like this:

Error:(16) Error: "..." is not translated in "de" (German), "el" (Greek), "iw" (Hebrew) [MissingTranslation]

(where "..." is a string)

At the bottom, after a lot of errors of this kind, I see this:

Error:Execution failed for task ':app:lintVitalRelease'.
> Lint found fatal errors while assembling a release target.
To proceed, either fix the issues identified by lint, or modify your build script as follows:
...
android {
    lintOptions {
        checkReleaseBuilds false
        // Or, if you prefer, you can continue to check for errors in release builds,
        // but continue the build even when errors are found:
        abortOnError false
    }
}
...

The question

I'm not sure what's wrong and how I can fix it. On Eclipse I did it very easily. Missing translations shouldn't stop me from signing an APK...

To me it seems as if Lint is preventing the exporting of the APK, and that the reason is that I didn't translate all of the strings. Is that true?

Can anyone please help me? How can I fix this, so that Lint will show me just warnings instead? or a confirmation dialog if I'm sure I want to do it?

Android Solutions


Solution 1 - Android

The cleanest way to solve the problem is to disable Lint checks of missing translations for release builds only.

To do so add "disable 'MissingTranslation'" to your build.gradle file as shown below:

android {
    buildTypes {
        release {
            lintOptions {
                disable 'MissingTranslation'
            }
        }
    }
}

Solution 2 - Android

> To me it seems as if Lint is preventing the exporting of the APK, and > that the reason is that I didn't translate all of the strings. Is that > true?

Yes. Default option is lintOptions.abortOnError = true

> Can anyone please help me?

You should open the build.gradle file located at the main project module, or the generic folder if you do not have a module. Then add the suggested lines:

android {
    lintOptions {
        checkReleaseBuilds false
        // Or, if you prefer, you can continue to check for errors in release builds,
        // but continue the build even when errors are found:
        abortOnError false
    }
}

Some Lint warnings are by default turned to studio as errors, I don't actually know why, but in terms of translations I guess that is a way to "stop" you publishing an app that the translation is incomplete due to a last minute additions of some texts.

With the lintOptions checkReleaseBuilds abortOnError you set the checking of Lint not to run for release versions and also not stopping if an "error" is found. Below I explain where the Lint errors settings can be found, so if you want to go further you can go one step forward and read them one by one. Some of them provide helpful instructions for code optimizations.

> How can I fix this, so that Lint will show me just warnings instead? > or a confirmation dialog if I'm sure I want to do it?

There is also an option at the Android Studio settings to change any Lint error to Lint warning, but I never test that. I usually turn to the gradle solution.

The option is located at Settings > Inspections > Android Lint. For easy find open Settings and at the search (located at the top) type Lint translation there you can change the translation options appear at the left from errors to warnings.

An other option if your error strings never going to be translated is to add at your XML string files tools:ignore="MissingTranslation" either at the root item or at each non-translatable string.

Solution 3 - Android

Simple way to solve this Error

Just add following Code To do add "disable 'MissingTranslation'" to your build.gradle file as shown below:

...
  android {
      lintOptions {
          checkReleaseBuilds false
          // Or, if you prefer, you can continue to check for errors in release builds,
          // but continue the build even when errors are found:
          abortOnError false
      }
  }
  ...

OR You can also Add this:

android {
        buildTypes {
            release {
                lintOptions {
                    disable 'MissingTranslation'
                }
            }
        }
    }

Solution 4 - Android

You could try to open "Translations Editor" and set the string "..." as "Unstranlatable". You also must remove all translations of this string.

Solution 5 - Android

FWIW: If you don't plan on supporting other languages, then you don't need to disable the lint checks at all. Sometimes your project setup (or a library you're importing) may have accidentally - or intentionally - included a config to support additional languages by declaring a values- folder for that language like this for instance:

<your project source folder>/main/res/values-ar

This was the case for me so I simply removed the folder. But if you have no control over the offending library then one choice is to disable lint abortOnError as indicated in the accepted answer, or find a way to exclude 'library-imported' folders somehow. For the latter option you can start here

Solution 6 - Android

there is many solution but i tried

<string name="hello" translatable="false">hello</string>

It's the ignore attribute of the tools namespace in your strings file, as follows:

<?xml version="1.0" encoding="utf-8"?>
<resources
  xmlns:tools="http://schemas.android.com/tools"
  tools:ignore="MissingTranslation" >

  <!-- your strings here; no need now for the translatable attribute -->

</resources>

and from the Gradle

 release {
            lintOptions {
                disable 'MissingTranslation'
            }
        }

and

android {
     lintOptions {
        disable 'MissingTranslation'
    }
}

Solution 7 - Android

Working

             buildTypes {
                        release {
                            lintOptions {
                                checkReleaseBuilds false
                                abortOnError false
                            }
                            minifyEnabled false
                            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
                        }
                    }

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionandroid developerView Question on Stackoverflow
Solution 1 - AndroidyvolkView Answer on Stackoverflow
Solution 2 - AndroidmadlymadView Answer on Stackoverflow
Solution 3 - AndroidSnoopyView Answer on Stackoverflow
Solution 4 - AndroidvalentaView Answer on Stackoverflow
Solution 5 - Androidkip2View Answer on Stackoverflow
Solution 6 - AndroidNull Pointer ExceptionView Answer on Stackoverflow
Solution 7 - AndroidKeshav GeraView Answer on Stackoverflow