Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
VS 2015 Setup is installing the Android SDK Manager into %ProgramFiles(x86)%. This means that installing a new Android SDK manager will require elevation. If the user is running VS non-elevated we need to force the launching of the Android SDK Manager as an elevated process so it won't fail for the user later on when he tries to install a new SDK version.
This is now fixed in this build:
Verified Fixed with VS 2015 (23020) build and XVS Build 3.11.762
It looks like we might have to do the same thing for Xamarin Studio. New bug report filed: #33176