title: Should app extensions have their own Localizable.strings?
body: <p><em>Currently using Xcode 6.3</em></p>
  
  <p>In our (open source) <a href="https://github.com/mozilla/firefox-ios" rel="nofollow">application</a> we have two targets:</p>
  
  <ul>
  <li>Our main application 'Client'</li>
  <li>An action extension 'ShareTo'</li>
  </ul>
  
  <p>Both targets have localized strings via <code>NSLocalizedString()</code>.</p>
  
  <p>When I "Export for Localization", I see one <code>&lt;file&gt;</code> extension in the exported XLIFF file named <code>Client/Localizable.strings</code> that contains the strings for both the main application and the app extension.</p>
  
  <p>Same results when doing an export from the command line via <code>xcodebuild</code>.</p>
  
  <p>I am very sure that this export behavior changed over time: previously the strings from the app extension would end up in a separate <code>Extensions/ShareTo/Localizable.strings</code> entry in the XLIFF file. Not combined in <code>Client/Localizable.strings</code>.</p>
  
  <p>So now I am wondering, is this new and correct behavior? Does this mean that app extensions lookup strings in their parent's bundle?</p>