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.
Reported here: https://forums.xamarin.com/discussion/99424/classic-api-and-macos-high-sierra#latest
Crash text: https://gist.github.com/chamons/983fda874214d04a9c0ebf208214db6e
This is not classic related, it also happens on Unified 32-bit.
3.4 as well as 3.6.
This appears to be an Apple regression from b2 to b3:
An obj-c app with the following code:
CLLocationManager * mgr = [[CLLocationManager alloc] init]; (In a loaded proc in obj-c)
crashes in b3 but not b2 when run on a 32-bit Cocoa app.
Radar coming up soon.
Given the likely high visibility of this, I filed it also on open radar:
From radar: CoreLocation depends on a private framework GeoServices which invoke initCNPostalAddressStreetKey at static initializer time even in 32-bit, but Contacts which I assume it is setting up is 64-bit only.
This was fixed by Apple in Beta 4.
QA - This does not need validation.