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 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.
In the trial of Xamarin iOS for Visual Studio, you cannot select an image for Defaultfirstname.lastname@example.org, and it does not load the default black image, so the screen will render only a 3.5" display with black bars on the top and bottom, when iPhone 4" is selected.
This is not an issue if you copy the files to the mac and build/run with Xamarin Studio.
Running Visual Studio 2013. I have tried this on a MacBook Pro running Mavericks and a VM of Windows 7 Pro. I have also tried this under another account with a Mac Mini Mavericks and a PC running 8.1 Pro.
Corrected version of Visual Studio Addin to 3.1.224
Xamarin Build Host 126.96.36.199
Xamarin Studio 5.1.4
I have checked this issue with following builds:
Mac 10.8.4 and Lion 10.7.4 with Windows 8.1
Xamarin VS 3.1.228
When License is Trial on Windows. I am seeing iPhone Launch Image by default a black and when I deploy application to iPhone I am getting splash screen(black) while application launching. This is the screencast for the same: http://www.screencast.com/t/sMzBSTPWHAF
I am not able to reproduce this issue.
Ish, Could you please provide screencast of the problem which you are facing?
Marking the bug as Resolved Not_Reproducible.
Please feel free to reopen it if you can still reproduce the issue with current bits.