Bug 54986 - [VS-PropPage] Plist editor "Deployment Target" field only has latest iOS version and can't be manually edited
Summary: [VS-PropPage] Plist editor "Deployment Target" field only has latest iOS vers...
Status: VERIFIED DUPLICATE of bug 54802
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.5.0 (15.2)
Hardware: PC Windows
: --- major
Target Milestone: 15.2
Assignee: Bugzilla
Depends on:
Reported: 2017-04-10 20:53 UTC by Ben Beckley
Modified: 2017-04-11 21:41 UTC (History)
5 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 Ben Beckley 2017-04-10 20:53:23 UTC
XVS (bce212f/d15-2)
Reproducible in VS2013 and VS2015

Basically what the summary says. I need to open the plist file and change the value manually which defeats the purpose of having a plist editor.

Reproduction Steps:
1) Start Visual Studio
2) Select > File > New > Project > iOS > any template app (I used Metal Game (iPhone))
3) Open the Info.plist file in the plist editor
4) Expand the Deployment Target dropdown and also try to edit the field manually
Expected: All deployment targets should be available.
Actual: Just the latest deployment target (10.3) is present

env info: https://gist.github.com/BenBeckley/9ff27e380da14dd107e042f2a094a166
Comment 1 Maroš Klempa 2017-04-11 05:31:37 UTC
I encountered exactly the same problem after upgrading to Visual Studio Xamarin
Comment 2 Ben Beckley 2017-04-11 17:17:34 UTC
Thank you for the confirmation, Maroš.

I'd also like to make a correction on my original post. The build under test was (bce212f/d15-2).
Comment 3 Ben Beckley 2017-04-11 21:41:46 UTC
Let's work out of the Bug 54802 because there is more detail and value in that report.

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