Bug 11239 - Localization languages disappearing from Base.lproj
Summary: Localization languages disappearing from Base.lproj
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 4.0.1
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-03-18 17:51 UTC by Bryan Moulton
Modified: 2013-11-19 17:08 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Bryan Moulton 2013-03-18 17:51:26 UTC
I reference to case #28708

After following the steps outlined in the guide, the Base.lproj file no longer works in XCode after closing and re-opening.

1. Double click on XIB file in XS
2. Perform steps to localize in XCode
3. Switch back to XS: Project will be updated
4. Quit XCode
5. Double click on XIB file in Base.lproj folder in XS
6. XCode project no longer knows about the configured languages or existing translations.
Comment 1 Jeffrey Stedfast 2013-03-20 11:19:06 UTC
Gonna need more info. The document he talks about is for Storyboards only, not xibs... yet he says he's doing it with xibs.

No clue what he's talking about.

A screencast would be really helpful.
Comment 2 PJ 2013-11-19 17:03:56 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 Jeffrey Stedfast 2013-11-19 17:08:46 UTC
I guess we can close this