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.
User reports intermittent error when building a solution. Building each individual project in the solution does not seem to run into this issue.
**Steps to Reproduce:**
Nothing reliable yet.
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(379,2): mandroid error XA0020: Unable to launch daemon.
**Build Date & Platform:**
Attached is full version info and logs from the case reporting this.
Having multiple Visual Studios open might cause this.
Our team is also experiencing this without having multiple instances of Visual Studio open.
The logs don't entirely make sense to me.
Firstly, there's this NullReferenceException:
> Xamarin.VisualStudio.Shell.ShellPackage Error: 0 : [2015-01-10 08:04:22.0] Background task error
> System.NullReferenceException: Object reference not set to an instance of an object.
> at Xamarin.InsightsCore.PlatformServices.<>c__DisplayClass4.<GetDeviceInfoData>b__3()
> at System.Threading.Tasks.Task`1.InnerInvoke()
> at System.Threading.Tasks.Task.Execute()
Xamarin.Android does not currently use Insights, so this should be unrelated.
Then there's this SocketException:
> Mono.AndroidTools.AndroidLogger Error: 0 : [2015-01-13 17:04:33.2] [E:]: Error in device tracker
> System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:5037
> at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
> at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
> at Mono.AndroidTools.Adb.AdbClient.EndConnect(IAsyncResult asyncResult)
> at Mono.AndroidTools.TrackDeviceTask.Connected(IAsyncResult r)
This is generated because the connection to `adb` was lost, which could only be a problem if using `adb` in the first place. (Are you using `msbuild /t:Install`? Perhaps you could try `msbuild /t:SignAndroidPackage`?)