Bug 47084 - Unable to run iOS application on iOS Simulator using VS 2013 in debug mode
Summary: Unable to run iOS application on iOS Simulator using VS 2013 in debug mode
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: Highest blocker
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-11-16 07:38 UTC by Saurabh
Modified: 2016-11-16 19:07 UTC (History)
4 users (show)

Is this bug a regression?: Yes
Last known good build: XVS

ZipLogs (9.81 KB, application/x-zip-compressed)
2016-11-16 07:38 UTC, Saurabh

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 Saurabh 2016-11-16 07:38:52 UTC
Created attachment 18480 [details]

Steps to reproduce:
1. Create iOS template in VS 2013.
2. Run the application in debug mode on iOS Simulator.

Actual Result: Application not getting run and no simulator getting launch on build host. However this is working fine in Release mode.

Expected Result: Application should get run in debug mode.

Supplement Info:
Attached zip logs

Environment Info:
VS 2013 Update 5

Regression Status: This is working fine with stable XVS However, getting same Issue with XVS
Comment 1 Jose Gallardo 2016-11-16 11:21:09 UTC
Can you please confirm if this issue is also present in VS2015??
Comment 2 Saurabh 2016-11-16 11:42:40 UTC
This Issue is working fine with VS2015
Comment 3 Mohit Kheterpal 2016-11-16 19:07:06 UTC
This issue has been fixed with Cycle 8 XVS

Hence closing this issue.