I also experienced this after adding the ShareKit library to my project. As it turned out, the problem was that ShareKit had a localizable.strings file and that my own project included a file with the same name. I'm not sure why, but when you started the application, both of these two localizable characters were matched, not both. If you rename the localizable.strings file so that there is no conflicting file name, the problem should go away.
If you rename the localizable.strings file, you need to update the code that loads the lines from that particular string file using the NSLocalizedStringFromTable macro instead of NSLocalizedString. For example, I renamed ShareKit localizable.strings to ShareKit.strings and edited the first line of this method as follows:
NSString* SHKLocalizedString(NSString* key, ...) {
source share