"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 I got is Lint errors like (I even changed MissingTranslation erros in Lint from fatal to warning)

"auth_client_using_bad_version_title" 
is translated here but not found in default locale

And this error repeats in all "values-" folders I know that I can disable lint checking before exporting application. But is there any way to do it right without any hacks, errors and curses on Google developers? So I think this case in one of two things:

I'm idiot or
Google publish crap that doesn't allow to use another Google crap etc.

Just I updated google-play-services lib then I'm getting same problem — Prasanna, May 23 '14 at 05:37
There seems to be a bug where lint will flag this when your strings file is in the default `values` folder. I started receiving the error erroneously when I started using feature modules. — methodsignature, Oct 22 '18 at 16:25
Try this method: https://stackoverflow.com/a/53780805/7831470 — Sagar Giri, Jan 04 '19 at 05:15

score 27 · Answer 1 · answered May 28 '16 at 21:15

27

On the top of your strings file, change the <resources> to this:

<resources tools:ignore="ExtraTranslation" xmlns:tools="http://schemas.android.com/tools">

answered May 28 '16 at 21:15

Panthro

3,247
2
32
37

score 22 · Answer 2 · answered Nov 02 '18 at 12:00

22

Looks like some caching issue of Android Studio. For me File -> Invalidate caches/restarts fixed the issue.

answered Nov 02 '18 at 12:00

Dharmendra

33,296
22
86
129

1

I got this error after merge confilct in Git. Build > Clean Project didn't help, but Invalidate caches did. – CoolMind Feb 05 '19 at 09:18
Unfortunately, this is the go-to solution for most Android Studio issues. Worked for me. – vvbYWf0ugJOGNA3ACVxp Mar 29 '19 at 04:07
This is what you need to do if you added new strings to your "default" strings folder and you get this message. – user1608385 Jul 11 '19 at 18:28

score 13 · Answer 3 · answered Jul 06 '14 at 07:50

13

Goto

Window->preferences->Android->Lint Error Checking -->Correctness: Messages--> Extra Translations ------------>make it Fatal to Warning

answered Jul 06 '14 at 07:50

Prasanth T

165
9

score 11 · Accepted Answer · answered May 23 '14 at 05:44

11

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.

answered May 23 '14 at 05:44

Prasanna

526
7
18

score 9 · Answer 5 · answered Feb 04 '19 at 06:11

9

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

answered Feb 04 '19 at 06:11

Mester Hassan

538
5
10

Uwais A · Answer 6 · 2014-06-09T01:59:43.247

5

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.

edited Jun 09 '14 at 01:59

answered May 27 '14 at 13:36

Uwais A

737
6
23

In my case the `strings.xml` is located in `values` folder without any modifier and I still get the error. – pkuszewski Jan 22 '19 at 10:28

score 5 · Answer 7 · answered Nov 23 '18 at 18:30

5

i had the same problem.. and doing a "clean project" fixed the issue

answered Nov 23 '18 at 18:30

mapo

194
4
11

score 1 · Answer 8 · answered Jun 02 '14 at 10:06

1

All I did was to copy the 'auth_strings.xml' file from the English folder to the values folder as the default version was missing.

answered Jun 02 '14 at 10:06

Carlos F

190
3
10

score 1 · Answer 9 · answered Jul 06 '14 at 16:20

1

just change extra translation from fatal to warning.It worked for me.

Window--->Preferences--->Lint Error checking--->Extra Translation(in ID column)

answered Jul 06 '14 at 16:20

Subodh

11
1

score 0 · Answer 10 · answered May 17 '16 at 07:54

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
}

One Code Man · Answer 11 · 2019-01-08T19:52:54.077

0

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.

edited Jan 08 '19 at 19:52

answered Jan 08 '19 at 19:45

One Code Man

224
2
5

score 0 · Answer 12 · answered Jan 31 '19 at 14:04

0

I had the same problem that I couldn't solve. I just restart Android Studio, and had no error anymore.

answered Jan 31 '19 at 14:04

Killyox

99
5

score 0 · Answer 13 · edited Jun 20 '20 at 09:12

0

A very quick solution mentioned here for this-

Simply remove the offending line and re-add it.

edited Jun 20 '20 at 09:12

Community

1
1

answered Oct 08 '19 at 06:18

GouravJn

246
1
6
18

score 0 · Answer 14 · answered Oct 08 '19 at 06:40

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.

"auth_client_using_bad_version_title" is translated here but not found in default locale

14 Answers14

Linked