Bug 11759 - monodroid error XA0000: Unexpected error - Please fill a bug report
Summary: monodroid error XA0000: Unexpected error - Please fill a bug report
Status: RESOLVED DUPLICATE of bug 12938
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.6.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-04-12 10:43 UTC by Jeremy Kolb
Modified: 2014-01-10 16:38 UTC (History)
5 users (show)

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 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.

Related Links:

Description Jeremy Kolb 2013-04-12 10:43:56 UTC
I'm seeing this a lot and it prevents me from building.

2>C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(164,5): monodroid error XA0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com. Reason: System.IO.IOException: Directory C:\Projects\INS_Android_Mono_git\INS_Android_Mono\obj\Debug\__library_projects__\OsmDroid is not empty
Comment 1 Jeremy Kolb 2013-04-16 13:24:33 UTC
I'm still seeing this with the latest stable version. However when I look there is no __library_projects__ directory.
Comment 2 Jonathan Pryor 2014-01-10 16:38:48 UTC

*** This bug has been marked as a duplicate of bug 12938 ***