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.
Description of Problem:
When opening an axml-File an exception from type "Xamarin.AndroidDesignerException" is thrown in the Designerview.
The xmlview is empty.
But the axml-File is not empty( proved with an external programm(notepadd++)).
Steps to reproduce the problem:
1. Start or open an project (c# Mono for android)
2. Open an axml-File in "Resources/layout"
exception from type "Xamarin.AndroidDesignerException" is thrown
Display the view of the axml-File
How often does this happen?
OS: Window 7
exception is thrown after update monodevelop on version 3.0.2 and Mono for Android 4.2.3 (releasedate of update: 19.07.2012)
Could you please try with MonoDevelop 3.0.3?
If you still get the error, could I get a copy of the resources folder of the project or at least the file causing the problem? If you wish, you can attach the file in a private comment.
Upon opening an .axml file in MonoDevelop 18.104.22.168 MonoDevelop freezes. Everytime. When opening it via context menu it works (Right click/Open with/Code-editor).
When trying to load a project it freezes when the last file open was an .axml file. No way to get the project loaded again. (Visual Studio 2010 also crashes upon opening an .axml file)
OS: Win7 64bit.
@Marcel: that's likely caused by having installed the latest Android SDK version (API level 16), which is not supported by the designer. A hotfix will be released soon.
This issue also froze Visual Studio 2010 and 2012 RC and by removing API level 16 from the SDK Manager resolved the issue.
Removing API level 16 from the SDK Manager resolved the issue for me too. Thanks!