The problem background
Since the release of iOS 16.0 beta, we have been receiving a series of crash logs of our App, all of which occurred on iOS 16.0 beta, including:
- iOS 16.0 Beta4 (20A5328h)
- iOS 16.0 Beta3 (20A5312j)
- iOS 16.0 Beta3 (20A5312g)
- iOS 16.0 beta2 (20A5303i)
- iOS 16.0 Beta1 (20A5283p)
Other than these system versions, it has not yet happened on any other iOS version. We suspect this issue has to do with the internal logic of the iOS 16.0 beta.
Common characteristics of the crash
- This only happens in beta versions of iOS 16.0
- Exception information is the same:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000058
Exception Codes: 0x0000000000000001, 0x0000000000000058
VM Region Info: 0x58 is not in any region. Bytes before following region: 206997290920
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
commpage (reserved) 3032000000-7000000000 [255.2G] ---/--- SM=NUL ...(unallocated)
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [7705]
- The top of the call stack for the crashed thread is all these frames:
0 libdispatch.dylib 0x0000000186f68554 dispatch_source_set_timer + 32 (source.c:1389)
1 PrivacyAccounting 0x000000020f05632c -[PACoalescingIntervalTracker coalesce:] + 420 (PACoalescingIntervalTracker.m:101)
2 PrivacyAccounting 0x000000020f04af30 __22-[PAAccessLogger log:]_block_invoke + 360 (PAAccessLogger.m:209)
Reproduction
We've been trying and analyzing these crash logs continuously since we received them, but we haven't found a way to reproduce them, and we haven't found suspectable codes.
Expectation
We are urgently and sincerely seeking Apple's help. We would like to know:
- How can we developers avoid this crash?
- Is Apple aware of this issue and will fix it in the subsequent release of iOS 16.0?
Crash log