EXC_BAD_ACCESS (SIGSEGV) Crash

My app has been rejected several times by the review process due to a crash error on start. I cannot identify the issue and believe it to be device-specific for the review team member's equipment.

Any suggestions on how to attempt debugging this issue? I have tried the instruments/Zombie Objects since it appears to be a memory issue, but cannot come up with a fix. Then again, not sure what it is I need to fix lol.

I have deployed/tested this application across multiple iPad/iPhone devices without being able to replicate the crash on my end.

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

(see fully symbolicated crash log below)



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


This means that your program crashed because it accessed invalid memory. The memory address corresponds to nil.

Code Block
Thread 0 crashed with ARM Thread State (64-bit):
sp: 0x000000016b609840 pc: 0x0000000000000000 …


This is unusal. The pc register is 0, indicating that the invalid memory access was triggered by an instruction fetch. The most likely explanation is that you called a nil function pointer.

Code Block
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? … 0 + 0
1 myPFA … 0x1047f0000 + 85488
2 myPFA … 0x1047f0000 + 110652
3 SwiftUI … TabView.init+ 5725260 (selection:content:) + 288


Frame 0 highly the call nil aspect of this. Frame 1 is the code that actually did that call. It’s hard to tell what this is because the frame isn’t symbolicated.

My advice is that you symbolicate you log and that look at the code associated with frame 1 to see how it could possibly call nil.

For info on how to symbolicate, see Adding Identifiable Symbol Names to a Crash Report.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
EXC_BAD_ACCESS (SIGSEGV) Crash
 
 
Q