Bug 21068 - Bad encoding in MSBuild output prevents activation
Summary: Bad encoding in MSBuild output prevents activation
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.18.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2014-07-02 19:08 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-06-28 18:09 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 Mikayla Hutchinson [MSFT] 2014-07-02 19:08:16 UTC
As seen in https://bugzilla.xamarin.com/show_bug.cgi?id=20937

In some cases, the text encoding of the MSBuild output can be incorrect, which causes failure parsing activation errors:

    C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(182,5): mandroid error XA9005: User code size, 1992686 bytes, is larger than 65536 and requires a Indie (or higher) License.
Comment 1 Sergey Zhukov 2014-10-21 04:19:49 UTC
I updated Xamarin Studio to version 5.5.2 and it activation dialog still does not show.

I see similar message, after that "minimumEdition" error, but there is no activation dialog.

Just a question: what is the reason to use non-ASCII symbols in compiler output? Why not to change a Indie  to ASCII "Indie" word?

Also, windows-7 does not support UTF-8 in console and this can produce more other issues, with non-ASCII symbols were put to console. (In my environment console works in windows-1251 codepage mode. This is default setup)
Comment 2 Mikayla Hutchinson [MSFT] 2014-10-21 12:12:14 UTC
On reflection, I think this is an issue in the Android targets.

XS hosts the MSBuild engine and gets UTF16 strings directly from the logger. Most likely the issue is with the output of mandroid.exe being read by the Android build tasks.
Comment 3 Jon Douglas [MSFT] 2017-06-28 18:09:58 UTC
As per the blog for Xamarin for All:


I do not believe this bug remains as the activation is now handled through other means (MSDN). Thus I am marking this bug RESOLVED INVALID for the time being. If this is still an issue, please feel free to reopen the bug.