“auth_client_using_bad_version_title” is translated here but not found in default locale

Question

I\'m forced to use Google Play service (I need Location Service). So, after I wrote all code and tested application on device, i tried to export signed application. And all

Answer 1

In case, if you want to just pass the release process;

In Android Studio, through Gradle, you can disable "Lint Error Checking" during the release process.

Open your build.gradle(app) file and add the following code snippet inside the android tag.

    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
}

Answer 2

In Android Studio, Go to File> Invalidate Caches / Restart..., and click on Invalidate and Restart.

Answer 3

So the 'default locale' is the one with just 'values' with no modifiers like -af, -am, -en etc. The problem happens because there is no auth_strings.xml file in that folder so there is no fallback option and hence the error.

To fix it just copy the auth_strings.xml file from another of the values folders to be your default language. I'd suggest a common language like English or Spanish. I used English. This fixes the error for me. I guess they just forgot to put in a default language.

Answer 4

I got the temporary solution.

copy auth_strings.xml from values-en-rIN (locale values for INDIA you can use any locale) and paste it in default values folder.

Answer 5

Make sure you have the string in the default locale. If you have it, try to delete the error line in the strings.xml and undo the deletion. If the string.xml is from a lib, delete the lib, sync, undo the deletion and sync again.

If the above step did not work, clean the project.

Answer 6

Ensure you have the string in the default area. In the event that you have it, attempt to erase the mistake line in the strings.xml and fix the cancellation. On the off chance that the string.xml and fix the cancellation. On the off chance that the string.xml is from a lib, erase the lib, match up, fix the erase and adjust once more.

On the off chance that the above advance didn’t work, clean the venture.