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 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.
I have Windows 8.1 and Visual Studio 2013 Ultimate (RU-ru)
Sometimes xamarin generates some inadequate errors like at a screen.
It contains only number (mostly '1', sometimes '2') and no any more information.
There are no any errors in Output, this error does not have any affect on deploy neither.
Created attachment 5553 [details]
Created attachment 5554 [details]
Thanks for the bug report. We will try to replicate this issue, I suspect it might be related to the RU-ru culture settings.
Is there any chance you can post the output from the output window for Build, Debug and Mac Server Log.
It's extremly hard to reproduce, because it's complete random.
i rebooted and it's gone.
But it will appear again (i saw it several times) and i will provide required info then.
Created attachment 6391 [details]
screncast of error
error appears after publish on 2:15
Ok, i think i reproduced this error accidently
I add screencast of the problem (it appears around 2:15)
This error number show how many other messages and warning + 1
What did i do:
1) opened project - no problem
2) published it - no problem
3) opened some xml drawings - there appears messages
4) changed axml layout
5) published - error appeared
6) now it will persist until restart
I'm marking this bug report as resolved fixed. We've introduced some fixes on the .axml editor that should be already addressed the issue.
Please feel free to reopen the issue if you can still reproduce it with current bits.