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 tried to reproduce this issue but unable to reproduce. I am able to Build then Rebuild the solution successfully without any error. As shows in screencast: http://www.screencast.com/t/getaagg7vr
Please let me know if I have to follow any other steps to reproduce this issue.
Also if possible could you please provide Ide log and Build output.
For Ide log, Location: VS-> Help-> Zip Xamarin Logs
For Build Output, Location: VS-> View-> Output-> Select Build in drop down list and copy logs.
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Xamarin 3.9.289.0 (39a70ae)
Xamarin.Android 184.108.40.206 (49a04b966feb40dfdba49d57ba16249b66d606a6)
Xamarin.iOS 220.127.116.11 (3b3ef438017c7ecf486defa9e01567a5f2b3cb2a)
Xamarin.iOS Unified Migration 1.0
I'll add a couple similar-looking bugs here to help keep them all coordinated in case they have the same underlying cause.
Possible duplicate: bug 19708.
Likely duplicate: bug 26841.
This happens for me every time also, if I turn on Debug / Exceptions / Common Language Runtime exceptions
I'll have to retract that... it did work a couple of times ok after turning that off but then it came back. Coincidence I think.
As we've introduced several improvements since the bug was reported, I'll mark the bug as resolved fixed tentatively, so QA can verify.
Please feel free to reopen it if you can still reproduce the issue with current bits.