Bug 51745 - Creating a new iOS app and opening the iOS Application properties is causing VS2017 to crash
Summary: Creating a new iOS app and opening the iOS Application properties is causing ...
Status: RESOLVED UPSTREAM
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: High major
Target Milestone: 4.3.0 (C9)
Assignee: Emanuel
URL:
Depends on:
Blocks:
 
Reported: 2017-01-24 21:43 UTC by Ben Beckley
Modified: 2017-02-02 14:45 UTC (History)
5 users (show)

Tags:
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:
Status:
RESOLVED UPSTREAM

Description Ben Beckley 2017-01-24 21:43:31 UTC
Steps to reproduce:
1) Start VS2017
2) Create a new iOS app from a template
3) Open the iOS project properties
4) Select the iOS Application tab
5) Click the Deployment Target dropdown menu (not necessary, but seems to bring the issue forth)

Expected Result: The fields are blank if there is no XMA connection. The fields are populated with iOS versions if there is an XMA connection.

Actual Result: VS goes unresponsive and crashes or restarts.

NOTE: I have reliably reproduced this while an XMA connection was being established. The few times I attempted this after an XMA connection was established, there was no crash. But I wouldn't rule out the possibility of it happening.

screencast: https://www.screencast.com/t/MZUDmzc5he
env info: https://gist.github.com/BenBeckley/e729b05691805b3372063a42d31ec72b