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.
I've created a new Hello World app in v1.2.121 and I want to define an identifier and version number (right-clicking on the project in Solution Explorer, selecting Properties, and selecting iOS Application). These are not being saved and preventing me from debugging (see forum post: http://forums.xamarin.com/discussion/1547/unable-to-debug-in-simulator-on-mac-mini-from-windows-8) and causes the iOS Simulator to crash saying the simulated application has quit. Relaunching and switching SDK don't resolve the error.
Hi Doug G,
There will be a new PList editor in the next release that will fix most of the issues regarding to the iOS Application information.
However, I am about to leave this bug as CONFIRMED (not closed) since there are some features we have to improve, as the mac build host error reporting in the event the iOS simulator returned an typified error.
As a workaround until the new version is released you can edit the Info.plist file directly and add the required keys manually. Alternatively, the same can be done using Xamarin Studio on Mac.
Fixed on XVS 3.0.54
I have checked this issue and now I am able to save Identified and version and able to deploy application on simulator successfully as shown in screencast :http://screencast.com/t/FLZ99cbAqd26
Hence closing this issue.
Please let me know, if I have to check something else to verify this issue.