Bug 39611 - unexpected error - file bug report to xamarin - XA0000 - malformed name
Summary: unexpected error - file bug report to xamarin - XA0000 - malformed name
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Radek Doulik
Depends on:
Reported: 2016-03-14 19:30 UTC by Frederic Rudman
Modified: 2017-06-28 06:07 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

error log as requested (170.71 KB, text/plain)
2016-03-14 20:07 UTC, Frederic Rudman

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 Frederic Rudman 2016-03-14 19:30:32 UTC
Description of Problem: can't build a project

Project builds properly at old location.

We copied the folder to another location (same computer, same drive)

Cleaned All, then Build All and we get this error:
/Volumes/MacPro HD3/Insync/simplytel/Hardware, Software/IPA VM/IPA Runtime: Error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.ArgumentException: Malformed name (XA0000) (IPA-Runtime) monodroid

When we build the same source from the old location, all is well.

What's going on?

When we copied the full folder (including the .sln file), we didn't not change anything. Straight copy.

Why would this create a problem?

ps: instead of Xamarin Studio "asking us" to report the bug, how about a little "let's join 2016 UI practices" and report the bug directly to your systems? Too much for your developers?
Comment 1 Frederic Rudman 2016-03-14 19:32:05 UTC
...also, it's not the XML editor component, but there's so many, it wasn't clear to us what to select ('none' or 'don't know' would be nice options).
Comment 2 Greg Munn 2016-03-14 19:59:03 UTC
Could you please enable diagnostic build output (Preferences | Project | Log verbosity) and then attach the build log to the bug report. The build output is available from the Error and Warnings Pad.
Comment 3 Frederic Rudman 2016-03-14 20:03:03 UTC
see attached
Comment 4 Greg Munn 2016-03-14 20:05:04 UTC
Sorry, but I don't yet see any attachments on this bug report.
Comment 5 Frederic Rudman 2016-03-14 20:07:54 UTC
Created attachment 15399 [details]
error log as requested

included error log
Comment 6 Greg Munn 2016-03-14 20:24:22 UTC
Thanks. I'll pass this on to the Xamarin Android team. In the meantime, I wonder if the folder with the comma in it could be the problem?
Comment 7 Frederic Rudman 2016-03-14 20:38:35 UTC
replaced the part of the path that had a comma (Hardware, Software) with a dash (Hardware-Software) and the build succeeded.
Comment 8 Jonathan Pryor 2016-03-15 20:58:25 UTC
> I wonder if the folder with the comma in it could be the problem?

That has historically been a problem, because (IIRC?) at some point we attempt to pass a path as an Assembly Name (trying it as a path if the assembly name parsing fails), and the `,` makes it "look (enough) like" an assembly name that our check fails.

Radek: Could you please revisit the ScanAssemblies (and related) tasks and see if there's a way to improve the experience here?
Comment 9 Prashant [MSFT] 2017-06-28 06:07:08 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.