Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 3470 [details]
Contrast values in "Main Interface" dropdowns
When using the info.plist editor from the main environment (not in "Project Options" dialog), the "Main Interface" assignments are backwards. The "iPhone Deployment Info" -> Main Interface specifies <key>UIMainStoryboardFile~ipad</key> and "iPad Deployment Info" specifies <key>UIMainStoryboardFile</key>.
Create a Universal app.
Create a storyboard for iPhone called "iPhoneStoryboard"
Create a storyboard for iPad called "iPadStoryboard"
Open info.plist in main GUI editor.
In "iPhone Deployment Info" set "Main Interface" to "iPhoneStoryboard"
In "iPad Deployment Info" set "Main Interface" to "iPadStoryboard"
Open info.plist in text editor. Note keys for:
... "Project Options" dialog is fine ...
Open "info.plist" by Context-clicking Project / Options->iOS Application
Note that storyboards are properly associated iPad->iPad, iPhone->iPhone
Hmm... Well, apparently it's a transient problem, as somehow I fiddled around and things came back to as-expected. However, if you check the attached screenshot from the original, you can see that the issue (however it's triggered) is real.
I've tried to repro this a bunch of times and cannot do it again. It definitely *did* happen as the screenshot indicates, but I can't get the behavior.
marking as NEEDINFO until there's a way to reproduce it
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.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.