title: Parse Cocoapod breaks localization
body: <p>In an iOS project, I've updated this morning my pods to add a new one. The Parse iOS SDK also got updated in the process, and it <em>seems</em> like it broke my app's localization. </p>
  
  <p>Now, when I try to call <code>NSLocalizedString(@"A_LOCALIZED_STRING", nil)</code>, I always get <code>@"A_LOCALIZED_STRING"</code> in return.</p>
  
  <p>Even if I use the longer version of <code>NSLocalizedString</code> with a specific bundle (here, <code>[NSBundle mainBundle]</code>), I get the same results.</p>
  
  <p>I've noticed that the only string that gets localized properly is the string <code>@"OK"</code>, which precisely is the only string specified in Parse SDK's Localizable.strings file.</p>
  
  <p>My interpretation is that this pod's Localizable.strings is somewhat overriding my own. Is that even possible? How to workaround this?</p>
  
  <p>Thanks!</p>
  
  <p>(I must also add that localization in my project used to work flawlessly until now, so it's not a first-time configuration problem.)</p>