Bug 25013 - Xamarin does not locate Android SDK when not under Admin
Summary: Xamarin does not locate Android SDK when not under Admin
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2014-12-02 16:42 UTC by James
Modified: 2015-01-14 05:20 UTC (History)
3 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 or GitHub 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 James 2014-12-02 16:42:54 UTC
From a Customer:

Both the Android SDK and NDK are installed on the machine in question, they are trying to set up a student Lab for multiple users on the same machine. The admin account can locate the Android NDK and SDK but for those that do not have admin rights it does not show as installed.

There was an attempt to add the Xamarin Developer folder to System/Library/Developer but the software errors after defining that location under another account.

Is there an alternative way to set up a Lab based machine and have it detect Android SDK/NDK installations?

Potential workaround:
Make the Xamarin developer folder, with permissions modified for Read & Write for all users, copied to a central location so that non-admin users can then copy to their user profile developer folders, then edit the path in the Android SDK Manager).  This seems to be working but is not really a great solution, as each user then needs to download additional SDKs if needed, instead of adding once per machine.
Comment 1 Greg Munn 2014-12-02 16:52:12 UTC
I'm not sure about this, I'm going to suggest that this might come under the purview of either the installer or XA.

Also, is this on Mac or Windows? The bug says Windows but you're mentioning a Mac path, it would be good to know for sure which OS we're talking about, although I suspect there may be similar issues for each OS.
Comment 2 James 2014-12-02 17:14:18 UTC
Sorry this is Mac specific, I had that wrong updated accordingly
Comment 3 Mikayla Hutchinson [MSFT] 2014-12-16 14:57:04 UTC
This is because the installer installs the Android SDK to the current user's home directory.

You can install the SDK anywhere on the machine and manually configure it in XS preferences.

If you install the SDK on Windows using the official Google installer, there is a registry key from which we automatically detect its location. However, there is no equivalent on MacOS.
Comment 4 Udham Singh 2015-01-14 05:20:49 UTC
Thanks Michael

As per comment 3 this issue has been answered by Michael. Hence marking this issue as RESOLVED-ANSWERED.