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 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.
This bug is primarily inspired by the following Forum post:
It seems that the _SetupApplicationJavaClass target depends on the _SetupInstantRun target in which this target will eventually invoke an `adb.exe` during the GetPrimaryCpuAbi Task. This seems slightly odd given that there is no "opt-in" into the Instant Run feature.
This can be seen in the following MSBuild Structured Log Viewer:
One observation I've made is this Task gets invoked regardless of if a device is plugged in. If a device is plugged in, you will see the Task use `adb.exe` to retrieve the Abi and SDKVersion.
Thus, is it expected that _SetupInstantRun runs regardless of a customer opt-ing into the feature via their project settings? I suspect that _CheckInstantRunCondition has an issue that defaults _InstantRunEnabled to true
The customer had noted that in Xamarin.Android 220.127.116.11 this behavior is not present. This is mainly because this build is almost 9 months old, and there has been work towards _SetupInstantRun since that build.
Xamarin 18.104.22.1684 (f42aa37)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 22.214.171.124 (c9880f9)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.Android SDK 126.96.36.199 (c9880f9)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS 10.4.0.102 (20d957a)
Visual Studio extension to enable development for Xamarin.iOS.
Xamarin.iOS and Xamarin.Mac SDK 10.4.0.102 (20d957a)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
We are experiencing the same problem on our TFS 2015 Build VM.
Adb.exe holds a handle to our Xamarin android project´s source folder. So the TFS build stucks during cleaning the workspace before compilation.
We are using Xamarin.VS 188.8.131.52.
I'll be taking a look at this first thing on Monday.
I believe that this bug was already fixed in monodroid/e95facca and released as part of Cycle 9.
I would suggest that they upgrade to XamarinVS 4.3.x (C9).
For reference this is the bug from the initial report https://bugzilla.xamarin.com/show_bug.cgi?id=43880