Xamarin.Facebook.iOS 7.1.1 causes SIGSEGV

[smallcandles]

I'm currently using version 5.12.0 of this nuget package successfully. When I updated to 7.1.1 I started getting crashes in my app at relatively random times. Unfortunately attaching a debugger wasn't helpful as the app closes when the problem occurs without any information printed to the debugger. Note that I am not performing any tasks related to the Facebook functionality when this crash happens. Reverting to 5.12.0 fixed the problem.

Analytics data on the phone (iPhone 8 iOS 13.6.1 although I also saw it on an iPad).

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000

I verified the same problem happened in Xamarin 4.6, 4.7, and 4.8

[gerardvanderkruijs]

I'm having the same issue, going to revert also to 5.12.0 for now.

[Lelelo1]

I get a crash when instantiating PlacesManager, probably not related though

[LeadAssimilator]

I'm also experiencing a similar crash. In my case, it appears to happen when a NullReferenceException is thrown by managed code - even if the exception is caught, the app just dies. Having the debugger attached makes no difference - the debugger doesn't even notice the exception was thrown or that the app even died.

Downgrading to 5.x makes everything work as expected where a NullReferenceException can be thrown, caught and break on throw while debugging without the app crashing.

[dev-xam]

I have exactly the same problem. After updating from 5.12.0 to 7.1.1 random crashes appears, usually just after application start. In debug mode and release mode (simulator or real device) no such crash happens, but after build and send release to AppStore for review or testflight - crashes happens. This is a tricky scenario.

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000 VM Region Info: 0 is not in any region. Bytes before following region: 4309958656 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START --->
__TEXT 100e4c000-100f84000 [ 1248K] r-x/r-x SM=COW

I have desymbolised crash log from Apple: plcrash::MS::async::dwarf_cfa_state_iterator<unsigned long long, long long>::next(unsigned int*, plcrash::MS::async::plcrash_dwarf_cfa_reg_rule_t*, unsigned long long*) (in SAMPLEAPP) + 14670932

After reverting to version 5.12.0 everything works good.