Bug 51713 - Profiler doesn't start if path to SDK location set in XS/VSforMac is wrong
Summary: Profiler doesn't start if path to SDK location set in XS/VSforMac is wrong
Alias: None
Product: Profiler
Classification: Xamarin
Component: Mac ()
Version: 1.0.x
Hardware: PC Mac OS
: High normal
Target Milestone: 15.1
Assignee: Rodrigo Moya
Depends on:
Reported: 2017-01-23 17:44 UTC by Alexander Köplinger [MSFT]
Modified: 2017-03-01 13:10 UTC (History)
5 users (show)

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

Profiler log (2.67 KB, text/plain)
2017-01-23 17:44 UTC, Alexander Köplinger [MSFT]

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 Alexander Köplinger [MSFT] 2017-01-23 17:44:40 UTC
Created attachment 19448 [details]
Profiler log

Repro steps:
1. Open XS or VS for Mac
2. Open Preferences->SDK Locations->Apple
3. Enter a wrong path into the Location field like "foo" and click OK
4. Try to open the Profiler, it errors out with "This library only works with Xcode 7 or newer."

I've attached the profiler log.
Comment 1 xamarin-release-manager 2017-02-24 09:27:29 UTC
Fixed in version (master)

Author: Rodrigo Moya
Commit: ee5d442ab42833f7cf021d6f9cf4febe32ab10f4 (xamarin/profiler)
Comment 2 asimk 2017-02-24 11:02:14 UTC
This issue has been fixed with Profiler Master build i.e. 1.3.1-106

Screencast: http://www.screencast.com/t/xKsjOxPZyR

@Rodrigo, Could you please merge this fix with C9 build.

Comment 3 Rodrigo Moya 2017-02-24 13:43:47 UTC
Not sure we'll be merging this fix into the cycle9 branch, only if we need to do a release, so I would mark it as verified with the master build (1.3.1.*)
Comment 4 Swati Gangrade 2017-03-01 13:10:21 UTC
Bug is retested and verified in below configuration
Mac Sierra OSX version-10.12
Profiler version : profiler-mac-1.3.1-116

Actual Result is working as Expected as shown in the Screencast: http://www.screencast.com/t/xKsjOxPZyR