NSLocalizedString wrongly detects all translations as missing

In AppCode 3.1 the NSLocalizedString detected translations that were missing in Localizable.string. Version 3.2 marks all translations as missing. If I open up Localizable.string file it still correctly detects which translations are not being used in the project. Any way to solve this?

1 comment
Comment actions Permalink

Hi Miha.

Thanks for reporting. We have some problems with NSLocalizedString in AppCode 3.2. Feel free to comment or upvote the issue: https://youtrack.jetbrains.com/issue/OC-12253


Please sign in to leave a comment.