Try 10.2 - I recall the 10.2 beta notes mentioning something about localization...
When things don’t work, is that because the built app doesn’t include the right localised resources? Or are all the localised resources present but are somehow not being used at runtime?
To test this:
Wait for the problem to happen.
Save a copy of the broken built app.
Do a clean build.
Confirm that it fixes the problem.
Save a copy of the working built app.
Compare the apps from steps 2 and 5.
Share and Enjoy
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"
Thanks KMT and eskimo. I've updated Xcode to 10.2. The problem seems to persist.
The issue is random, and it happens with all the resources present at runtime. I'll definitely try comparing the 2 built apps, I hadn't thought of that.
Thanks a bunch!
Did you solve your problem ? If yes, thanks to feedback how you solved and close the thread on your (correct) answer.
If not, hope this will help.
When it occurs, does it affect all strings ?
What are the languages you use as localization languages ?
When it occurs, if you switch language, what do you get ? Correct strings or capitalized strings ?
I remember an old problem I had a bit similar.
- it came from the fact that I had extraneous (don't ask me why) .strings files.
Could you check all the .strings files you have in project and see if they are at the right place ?
Another hint: a missing semi colon at the end of a resource in a .strings file causes problems for localizer.