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.
A customer on IRC #monotouch noted to me that when he upgraded to MonoTouch 5.0 from an old install of MonoTouch, that it failed due to the old license file being in the way and that it took him a while to figure out how to fix that issue.
He suggested that we document that users upgrading should move that license file out of the way first, but I think we should do better: we should auto-rename that file (License.v2.bak?) or ask the user or something, we don't want to require our users to have to dig up documentation on these sorts of failures.
Going to consider this fixed now unless we get actual specifics.