无法从 Localizable.strings 文件中检索本地化的字符串

Question

I'm unable to get the correct localized german strings from the Localizable.strings file. My app setup looks like this

• Main.storyboard

  • Main.storyboard (Base)
  • Main.strings (German) -> these strings are translated correctly

• Localizable.strings

  • Localizable.strings (English)
  • Localizable.strings (German) -> can't get these strings

Inside the app I'm trying to get the string like this

NSString *item = NSLocalizedString(@"Group expenses", @"Menu item");

The Localizable.strings (German) file looks like this

/* Menu item */
"Group expenses" = "Gruppenausgaben";

When I set a breakpoint after item I always get the English string back, however the path for the resource seems correct NSString *path = [[NSBundle mainBundle] pathForResource:[[NSLocale preferredLanguages] objectAtIndex:0] ofType:@"lproj"]; gives me: /data/Containers/Bundle/Application/5E3ED6BF-71E1-4C60-9EDA-610C9A32B8EF/MyApp.app/de.lproj

I also have localized the string file

It's also included in Copy Bundle Resources

I tried several answers from different questions here on stackoverflow, like deleting app and do a clean (shift+cmd+k), setting application language under Edit Scheme , ...

Answer 1

Ok, I think I know the reason for your bug. Parse had an issue with adding Localizable.strings as documented here . This was fixed in 1.8.1 version of their framework:

V1.8.1 — AUGUST 19, 2015

...

Fixed: Overwritten localizations when used via CocoaPods and integrating as static library.

...

You can also check this question.

So, just make sure you use the latest version of the framework and all should work :)

Answer 2

I encountered a same problem before, some approach you can try:

• Make sure you set German as your iOS device system language.

• Run this app in Xcode, then stop. Launch the app from the iOS device manually. (First launch with Xcode will use base language, I don't know why)

• See if it works

Answer 3

Just had a similar issue was cracking my head, do a search of the xx.strings file I had an old copy of the bloody file messing me up.

find ./ -name "xx.strings" -print

double check your string file is proper

plutil -lint  xx.strings