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.
Just created my first project with Xamarin.Android. Compiles OK, but when I want to run it, this error shows up:
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(5,5): Error XA0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com. Reason: System.IO.DirectoryNotFoundException: Directory 'C:\Users\FrÃ©dÃ©ric\Documents\Projects\ZinioArchiver\ZinioArchiver\bin\Debug' not found. (XA0000) (ZinioArchiver)
The correct path should contain "Frédéric" instead of "FrÃ©dÃ©ric". I suppose there is an invalid encoding somewhere.
I'll try to use the 8.3 notation in the future as a workaround...
Please enable and provide Diagnostic build output:
Created attachment 4447 [details]
Output of MSBuild
@Frédéric: I don't think Attachment #4447 [details] is Diagnostic build output, as it doesn't contain the `mandroid` command that's being executed.
I have created a new folder with a plain name (D:\Xamarin) for placing my projects instead of the default VS2K12 project folder (C:\Users\Frédéric\Documents\Visual Studio 2012\Projects) and that solved my issue.
You can easily reproduce the problem by using a special character in the path to the Xamarin project, but in my case, this workaround solved the issue, so as far as I'm concerned, you can close the call.
Just to do a little bookkeeping: this is most likely a duplicate of bug 14918.
*** This bug has been marked as a duplicate of bug 14918 ***