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.
When building a Xamarin.Android project, the following error appears:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets (_ExtractLibraryProjectImports target) ->
: monodroiderror XA0000: Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com. Reason: System.TypeInitializationException: An exception was thrown by the type initializer for Xamarin.Android.Tools.AssemblySignature ---> System.Security.Cryptography.CryptographicException: Couldn't decode XML ---> System.StackOverflowException: The requested operation caused a stack overflow.
Time Elapsed 00:00:00.2464440
Xamarin Studio 4.0.10
A repro or additional information would be nice. Which version of OS X does this happen on?
I have encountered the same problem as reported, here are the version details:
4.0.12 (build 3)
Package version: 302030000
4.8.1 (Starter Edition)
Supported Android version:
2.2, 2.3, 4.0
Java version: 1.7.0_40
220.127.116.11 (Starter Edition)
Mac OS X 10.8.5
@W.C.: What happens if you run the following command within Terminal.app?
mandroid 18.104.22.168342252 Starter
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.