Run ARSession crashed

Run ARSession crashed

Please post a full crash report, per the instructions in Posting a Crash Report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Fatal Exception: NSRangeException 0 CoreFoundation 0x99288 __exceptionPreprocess 1 libobjc.A.dylib 0x16744 objc_exception_throw 2 CoreFoundation 0x1a4318 -[__NSCFString characterAtIndex:].cold.1 3 CoreFoundation 0x3792c __NSDictionaryMutablePlaceholder 4 ARKitCore 0x2ffa0 -[ARParentImageSensor start] 5 ARKitCore 0x10f29c -[ARSession _startSensorsWithRequiredDataTypes:optionalDataTypes:] 6 ARKitCore 0xce14 -[ARSession _updateSessionWithConfiguration:options:] 7 ARKitCore 0x108ad0 __42-[ARSession runWithConfiguration:options:]_block_invoke 8 libdispatch.dylib 0x1e6c _dispatch_call_block_and_release 9 libdispatch.dylib 0x3a30 _dispatch_client_callout 10 libdispatch.dylib 0xb124 _dispatch_lane_serial_drain 11 libdispatch.dylib 0xbcb4 _dispatch_lane_invoke 12 libdispatch.dylib 0x16500 _dispatch_workloop_worker_thread 13 libsystem_pthread.dylib 0x10bc _pthread_wqthread 14 libsystem_pthread.dylib 0xe5c start_wqthread

Same issue here. iOS 15.6.1 iPhone 11

The result we monitored is that only iOS15.6 users have this problem.

@ Developer Technical Support

Stack trace

I’m sorry but I can’t make any progress with what you’ve posted. Please read the instructions I referenced earlier and post your full crash report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Happened to our users as well, Crash is attached.

Unfortunately there are limits to what I can do with a third-party crash report. Consider this:

Fatal Exception: NSRangeException
0  CoreFoundation  … __exceptionPreprocess
1  libobjc.A.dylib … objc_exception_throw
2  CoreFoundation  … -[__NSCFString characterAtIndex:].cold.1
3  CoreFoundation  … __NSDictionaryMutablePlaceholder
4  ARKitCore       … -[ARParentImageSensor start]

Frames 2 and 3 seem to be critical here, but how much can I trust the symbolication? It’s seems hard to see how you’d go straight from __NSDictionaryMutablePlaceholder in frame to NSString in frame 2. It’s possible, I guess, but just hard to see.

With an Apple crash report I get function offsets so I can evaluate whether these symbols look OK. I also get a Binary Images section so that I can try resymbolicating. With this crash report I get neither, and thus I’m stuck.

If you can find an Apple crash report for this, please post that. And ideally you’d disable your third-party crash reporter so that I can trust the Apple crash report [1].

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] If you’re curious as to why I don’t trust third-party crash reports, see Implementing Your Own Crash Reporter.