Localizable.strings not working in iOS

Question

I'm having this really mind breaking problem.

I created a Localizable.strings file in XCode and then 2 languages in it.

I filled up these files with the language translations, did a build/clean and then a fresh build, but there is no way the Localization strings show up in my project. If I try something like:

self.title = NSLocalizedString(@"HEAD", nil);

only "HEAD" instead of the translation shows up in the device simulator.

This is my project hierarchy:

project hierarchy

And this are the content of the English localization file: enter image description here

Any ideas?

This [answer](http://stackoverflow.com/a/8851669/384808) to a similar question might help you. — Brian Driscoll, Jun 25 '12 at 18:17
In my case I have replaced the file name with default name `Localizable.strings`. Now it is working fine.In my project so many pods with language changes, so it is not reloading immediately, after second time reopening the app then it's working. So I have replaced with default file name `Localizable.strings`. — Naresh, Dec 19 '22 at 16:47

score 82 · Accepted Answer · answered Jun 25 '12 at 18:58

82

I found the answer myself.

Besides cleaning and building the project again and all that I described above. You must also delete the app in the iPhone simulator and then build it again! After that it works perfectly.

Talk about making it simple Apple...

answered Jun 25 '12 at 18:58

jbssm

6,861
13
54
81

5

Is this only a problem for the simulator or will users on App Store also have to delete the app to get the new language to work? Thanks. – geekinit May 04 '13 at 18:51
@geekinit I didn't test the app in a physical device, so I don't know the answer to that question. I would like to know the answer if you get it tough. – jbssm May 05 '13 at 19:34
2

Thanks for this. Deleting the app, cleaning and re-installing it worked for me. – Brian Boyle Aug 21 '13 at 10:41
In my case all other cases did not work at all. And complier does not show any warning/error in Localizable.strings file. Then I have started my key value format as "key" = "value"; And I found some my stupid mistake which was in format that was "key"; = "value"; Note : there was a extra semicolon (*) after key . After removed that I localisation works like a charm. Very easy way to catch your format. Just comment entire file's key value pairs. Then just put a key value and run the code. I think you will get know what is the actual issue. Thanks Guys. – Ravi Jul 10 '17 at 19:50
I have tries all things, Deleted app and reinstalled it and also check the entire file there no problem of semicolon though i don't get the arabic string in some places. @jbssm – Parth Barot Aug 20 '18 at 14:05
Thanks mate, that was exactly that worked for me ! – Sangsom Oct 25 '21 at 13:02

score 42 · Answer 2 · answered Jan 26 '15 at 19:58

42

Be sure that:

The file is called: "Localizable.strings".
"Localizable.strings" belongs to the target you are dealing with.

answered Jan 26 '15 at 19:58

Javier Calatrava Llavería

9,493
4
53
47

2

Thanks :) This solved my issue. Had the file named Lozalizable.strings. Wouldnt notice it without your post! – Adam Studenic Dec 24 '15 at 13:54
5

I LOL'd at "Lozalizable" – Paula Hasstenteufel Mar 16 '17 at 20:31
1

Yes, be sure that your file name IS NOT "Localization.string", I had the same problem and after I changed it to "Localizable.string" it worked fine :) – Mihai M. Jun 07 '17 at 08:56
In my case, The Localizable.strings is not assigned to the Target,Thanks! – Randall Wang Dec 06 '18 at 07:24

score 21 · Answer 3 · answered Sep 03 '16 at 10:23

21

A few checks:

Make sure the filename is exactly Localizable.strings and is included in the target
Every string is ended with ;
Every string is double quoted with "
Comments begins with // (NOT #)

answered Sep 03 '16 at 10:23

samwize

25,675
15
141
186

score 14 · Answer 4 · answered Oct 16 '14 at 11:33

14

Make sure you have Localizable.strings under Build Phases, Copy Bundle Resources.

answered Oct 16 '14 at 11:33

irmakoz

1,166
2
12
21

1

Actually i was missing this, thanks! this should be upvoted – damuz91 Jun 16 '16 at 00:49

score 5 · Answer 5 · answered Oct 14 '15 at 11:59

5

Check the file name if the first letter is Uppercase Localizable.strings

answered Oct 14 '15 at 11:59

Blazej SLEBODA

8,936
7
53
93

score 3 · Answer 6 · edited May 23 '17 at 11:47

3

@jbssm's solution works, but a better way (making sure the resource will keep updating without cleaning and deleting each time) will be to add a custom script build phase that changes the access time of the Localizable.bundle.

As described in https://stackoverflow.com/a/19274844/414037

edited May 23 '17 at 11:47

Community

1
1

answered Jan 22 '14 at 15:36

yonix

11,665
7
34
52

score 2 · Answer 7 · answered Jan 29 '14 at 08:09

2

I found 1 answer myself.

Make sure that all the values have end point with ; Otherwise,its not work..

answered Jan 29 '14 at 08:09

Hrushikesh Betai

2,227
5
33
63

8

Your project will not compile when there is a ';' missing – Jasper Aug 04 '15 at 09:01
1

This answer is correct for those who use storyboard localizations. If you have a missing `;` in your storyboard localizations , project will compile fine but won't load localizations at runtime. However if you are using localizable.strings it will give an error if there's a missing `;` – Rukshan Jun 11 '16 at 11:29

Aron · Answer 8 · 2018-10-31T13:29:50.377

2

Besides all the tips mentioned elsewhere in this thread, Localizable.strings also has to be located in the project root folder in certain cases.

edited Oct 31 '18 at 13:29

answered Aug 28 '18 at 16:07

Aron

3,419
3
30
42

score 0 · Answer 9 · answered Aug 30 '16 at 15:37

In my case, my Localizable.strings file was not properly formatted, due to some left over text. The compiler did not complain, but all the strings after the illegal section of the file were ignored. My file looked something like this:

"Key1" = "String1";

A string
A string
A string

A string";

"Key2" = "String2";

So be sure to hand inspect any Localizable.strings that is not being processed properly. You cannot trust the compiler to catch all formatting errors.

Got same error. Use the following command in terminal to find the line: plutil -lint — Kusan, Aug 25 '17 at 14:45

score 0 · Answer 10 · answered Aug 16 '17 at 12:47

My two cents on localization. I have tweaked with the localization files, added and removed them, and had the project gone under many Xcode updates. Later find that except English none of the localization is working.

The problem was I must have a base localization, I must tick the base on the right side when I did that a file in left added and other translation comes up in the app. Surely have the strings there...

user3108511 · Answer 11 · 2018-07-04T05:18:44.077

Replace the position of Localizable.strings
Have a cross verification with Localizable.strings cut and past in note pad so that we can easily identify the hidden characters and sublime texts. resolve it the follow the bellow steps.
Make sure the filename is exactly Localizable.strings and is included in the target
Every string is ended with ;
Every string is double quoted with "
Comments begins with // (NOT #)

Also delete the app in the iPhone simulator and then build it again! After that it works perfectly.

score 0 · Answer 12 · answered Jul 19 '19 at 09:50

0

I also had to set the encoding of given .strings file.

To do this select the file in project navigator and then on the right panel select encoding in "Text Settings" section. I used Unicode(UTF-8).

answered Jul 19 '19 at 09:50

Chuck Boris

1,275
1
11
9

score -1 · Answer 13 · answered Oct 22 '19 at 09:11

-1

I want to warn on one more possible problem related to UIButton, who can look like localization is not working.

In order to set text on UIButton use:

setTitle(_ title: String?, for state: UIControl.State)

Instead of:

button.titleLabel?.text

answered Oct 22 '19 at 09:11

slobodans

859
1
17
23

Localizable.strings not working in iOS

13 Answers13

Linked