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 for Bug 3117 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
If you have a Mapview control to a view but do not wire up an instance variable to it you'll get a runtime crash on the device as shown:
exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named MKMapView'
The workaround is to just wire up an instance variable to the control in the NIB. I guess at that point mono touch realizes it needs to link in the map kit library.
I realize most people will want to hook up the variable but when you are initially laying out your screen you may not do this and then get the above crash and waste a lot of time tracking it down.
This is a good suggestion; We will have to update our linker to reference frameworks that are listed on XIB files, even if they are not referenced in the code.
MMmmm... Still with the same problem. Is this closed?
(iPhone 3GS with iOS 6.03)
*** Bug 13561 has been marked as a duplicate of this bug. ***