Bug 3859 - Cannot change Android SDK location using VS.
Summary: Cannot change Android SDK location using VS.
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: High major
Target Milestone: ---
Assignee: Jonathan Pobst
URL:
Depends on:
Blocks:
 
Reported: 2012-03-12 13:43 UTC by PJ
Modified: 2016-08-03 15:23 UTC (History)
7 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:
VERIFIED FIXED

Description PJ 2012-03-12 13:43:19 UTC
Steps to reproduce:
1 Open VS Options
2 Go to Mono for Android options
3 Change the SDK path and hit OK
4 Restart Visual Studio


Expected behavior:
Android SDK location has changed to the value I set (or I am told that it is an invalid location)

Actual behavior:
Android SDK location reverts to previous (default) value.

http://screencast.com/t/edRjamr9NsfS



This bug was also filed on Desk.com, #8657.


I experienced this on:
MfA 4.0.4
VS 2010
Comment 1 PJ 2012-03-12 15:48:54 UTC
This issue prevents users from switching to the default android SDK location if they install the Android SDK separately from MfA.

One workaround for this bug is to delete your MfA 'PrivateAndroidSdkPath' registry entry.  This should only be undertaken after a registry backup and if you are familiar with regedit.

Disclaimer:  Use Registry Editor at your own risk. If you use Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. 

Full key path: HKEY_CURRENT_USER\Software\Xamarin\MonoAndroid\PrivateAndroidSdkPath

This will force VS to look for the android-created registry key and locate their SDK location. 

NOTE: Ensure you have set up the other Android SDK location with the desired SDK versions etc.




Overall though, this issue should be resolved with an option for a unified Android SDK location during installation.

Can we look into checking for the Android SDK location on install?
Comment 2 Jonathan Pobst 2012-04-19 18:02:08 UTC
Fixed in 4.1.1.

The settings panel is now much nicer, and setting the Android SDK should actually work.

ed3aae159c36427b7f927d876789e772314e35c7
Comment 3 Mohit Kheterpal 2014-01-24 07:20:35 UTC
We have checked in VS2010 and user is able to change Android SDK location.
Screencast for this: http://screencast.com/t/EkHLZKpt

Environment info:
Xamarin Studio
Version 4.2.3 (build 154)
Build Information
Release ID: 402030154
Git revision: 4dca4a28d7ecc2c4df8a4d58e74b8902d0283b53
Xamarin addins: cc120a6f639fa6649aa4d23a0f0e7c5701134047

Xam.Android 4.13.0-4 (window master)