Bug 11886 - Wrong version of the iOS simulator started
Summary: Wrong version of the iOS simulator started
Status: RESOLVED DUPLICATE of bug 11101
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-04-22 11:16 UTC by Sebastien Pouliot
Modified: 2013-04-22 14:08 UTC (History)
1 user (show)

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


Attachments
screenshot (53.07 KB, image/png)
2013-04-22 11:16 UTC, Sebastien Pouliot
Details


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:
Status:
RESOLVED DUPLICATE of bug 11101

Description Sebastien Pouliot 2013-04-22 11:16:05 UTC
Created attachment 3840 [details]
screenshot

Sometime* starting a project from XS loads the "wrong" (default?) iOS simulator version. It seems the value shown to the user does not match what mtouch is called with.

This leads to weird errors, e.g. 11835, where API and selector are reported as missing.

* seems to occurs when opening a project without using the XS comboboxes.
Comment 1 Jeffrey Stedfast 2013-04-22 14:08:54 UTC

*** This bug has been marked as a duplicate of bug 11101 ***