Bug 28432 - Disable ability to select the option to create an IPA for iPhoneSimulator builds.
Summary: Disable ability to select the option to create an IPA for iPhoneSimulator bui...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.9
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-03-25 20:42 UTC by Jon Goldberger [MSFT]
Modified: 2015-10-19 10:40 UTC (History)
4 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 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 Jon Goldberger [MSFT] 2015-03-25 20:42:58 UTC
## Description

In Xamarin Studio (Mac) it is impossible to select the option to build an IPA for the iPhoneSimulatorPlatform, but in Visual Studio you can... however the IPA is not built (expected as there is no need for a simulator build of an IPA). This may cause confusion as users might expect an IPA to be generated when it is not.

Would it be possible to disable the iPhoneSimulator platform so it can't be selected in the Platform drop-down in the Project Properties -> iOS IPA Options settings page?
Comment 2 Joaquin Jares 2015-10-19 10:40:20 UTC
We have that option enabled because we need to be able to unselect it if it's selected, and it would be weird to disable as soon as it is selected. We know it's not the best option, but it is absolutely by design.