1

I've developed quite a large project, but now I'm getting a silly issue all the time.

My localizations aren't always localized. Every second build they fail. Is this a known Xcode bug?

I'm running the latest version of Xcode.

James Webster
  • 31,873
  • 11
  • 70
  • 114
Lukas
  • 1,346
  • 7
  • 24
  • 49
  • When you say "aren't always localised", what do you mean? The build doesn't do the localization does it, it simply copies the localised files into the Application bundle. Have to checked if one or more localized files aren't being copied correctly? – trojanfoe May 08 '12 at 05:56
  • hello, thanks for the answer. Yes, the problem is, that these files are only copied once everv second build. This is not really anoying but one of my latest apps got into the appstore without the localization files and this was really anoying. – Lukas May 08 '12 at 06:23
  • Hmmm, I've never seen that issue myself. – trojanfoe May 08 '12 at 07:25

1 Answers1

2

It's probably because there are two localizable.strings files in your solution. It can easily happen if you drop in source files from another project (e.g. ShareKit). See this other question for an explanation and a solution: Localisation strings not always work having ShareKit in a project

Community
  • 1
  • 1
Clafou
  • 15,250
  • 7
  • 58
  • 89