Bug 52873 - XA auto-provisioning not working as expected
Summary: XA auto-provisioning not working as expected
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
Depends on:
Reported: 2017-02-27 22:09 UTC by Rodrigo Kumpera
Modified: 2017-06-27 20:39 UTC (History)
3 users (show)

Tags: bb
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 for Bug 52873 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Rodrigo Kumpera 2017-02-27 22:09:38 UTC
Zoltan is having a few issues with auto-provisioning in recent XA.
Comment 1 Zoltan Varga 2017-03-02 22:30:33 UTC
Some problems:
* XA installs a new system mono, which can break all kinds of stuff.
* Also, if I have two xa trees, will they keep installing their own mono versions
  back to back ?
* doing make mono will generate a cache file. Doing make clean in builds/ doesn't delete it, so doing make all in builds/ will use that instead of doing a rebuild.
* The .stamp file for android-sdk-tool is created even if the reset fails for some
  reason, leading to strange bugs later on.
* The reset target for android-sdk-tool should be called 'reset-android-sdk-tool' instead of 'reset-android-sdks'.