Bug 53108 - [XVS 2017-Dev15 RTW] Wrong simulator launched on Mac Machine with which Mac Agent is connected
Summary: [XVS 2017-Dev15 RTW] Wrong simulator launched on Mac Machine with which Mac A...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.3.1 (15.1)
Hardware: PC Windows
: --- major
Target Milestone: Future Cycle
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-03-07 11:47 UTC by Jacky Waswani
Modified: 2017-07-10 17:47 UTC (History)
8 users (show)

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


Attachments
ide logs attached. (9.85 KB, application/octet-stream)
2017-03-07 11:47 UTC, Jacky Waswani
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 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 NOT_REPRODUCIBLE

Description Jacky Waswani 2017-03-07 11:47:21 UTC
Created attachment 20176 [details]
ide logs attached.

Wrong simulator launched on Mac Machine with which Mac Agent is connected.

Build Details:
 - VS 2017 Enterprise 15.0.0.+26227.2.d15rel
 - Xamarin 4.3.0.784(74f58d6)
 - Xamarin.iOS 10.4.0.123(35d1ccd)

Steps:
1. Create an iOS single view app.
2. Connect to Mac agent and run in Debug mode with higher XCode version (latest)
3. Change Xcode path to lower version from mac machine and run the same app again on the then showing latest simulator from the list.(Need to restart and re connect Mac agent before this step.)

Expected result:
The Simulator which is selected from the drop down list should be launched.

Actual result:
The previously launched simulator is seen launched.
Comment 1 Jon Douglas [MSFT] 2017-07-07 18:34:54 UTC
Hi Jacky,

Can you please explain these two steps in depth?

2. Connect to Mac agent and run in Debug mode with higher XCode version (latest)
3. Change Xcode path to lower version from mac machine and run the same app again on the then showing latest simulator from the list.(Need to restart and re connect Mac agent before this step.)

I'm not sure what you mean by changing to a higher XCode version and then changing the XCode path to a lower version. Does this imply that you are switching between multiple XCode apps and potentially Xamarin.iOS versions if they are not compatible?

For example, can you please provide expanded steps between 2 and 3? Such as exact versions of XCode and Xamarin.iOS that is used? (If more than one).

Perhaps this scenario is running into a build cache or similar where the previously launched simulator is being launched. A few things to ensure are:

1. Is the obj/bin folders cleaned between builds?
2. Is the build cache on the build agent deleted and rebuilt?
3. Is the project freshly deployed after steps 1-2?

Thus I am setting this bug to NEEDINFO until this is reproducible. Thank you for the report!