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.
Created attachment 5400 [details]
I updated Xamarin.Android from Visual Studio 2012. After installation, I was no long able to open my project (iOS project) and was given this error (screen1.png). Additionally, when going to Tools --> Options --> Xamarin --> iOS Settings cannot be opened (screen2.png).
Created attachment 5401 [details]
@Seth, we are not observing this issue here with latest builds. If you are still
facing this issue, It would be great If you share your build details and logs
with us to reproduce this issue over here.
You can get logs from VS Help menu > Xamarin > Zip Xamarin Logs
and build information from Help > About Microsoft Visual Studio > Copy Info
Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Xamarin 3.11.666.0 (ebae43a)
Visual Studio extension to enable development for Xamarin.iOS and
Xamarin.Android 126.96.36.199 (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.Forms Intellisense 1.0
Provides intellisense for Xamarin.Forms in the XML editor.
Xamarin.iOS 188.8.131.52 (67b390d0d1bd741582cf7b7fd3ffea08583a3f83)
Visual Studio extension to enable development for Xamarin.iOS.
I'm closing this as no further information has been provided and we cannot reproduce similar issues with latest stable builds. Please feel free to reopen if the problem recurs.