Investigating SIGTRAP on AppDelegate Declaration during App Store Connect Review

Question

Created Sep ’20

Replies 4

Boosts 0

Views 1.6k

Participants 2

Hello Apple World,

The app review team is experiencing a crash when running my app. I am not able to reproduce this crash in the simulator, on my device, or in TestFlight.

The reviewers say the app crashes after the user signs in, but the stack trace points to this line in my AppDelegate.swift:

Code Block 15 class AppDelegate: UIResponder, UIApplicationDelegate {

I have three questions for the community:

Is there a way I can get more information from this crash report?
Does the app crashing on this line signify some general type of error I should investigate?
Why does the app only crash when the app review team runs it? Is there a way I can replicate their testing environment locally?

Thank you for your help,

Marvin

Code Block 
Release Type:        User
Baseband Version:    n/a
Report Version:      104
Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000001af0049d0
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [20706]
Triggered by Thread:  8
Last Exception Backtrace:
0   CoreFoundation                	0x1af3a3654 0x1af279000 + 1222228
1   libobjc.A.dylib               	0x1af0c5bcc 0x1af0c0000 + 23500
2   Foundation                    	0x1af8891fc 0x1af665000 + 2245116
3   Foundation                    	0x1af68c4a0 0x1af665000 + 160928
4   UIKitCore                     	0x1b38304b0 0x1b2a29000 + 14709936
5   UIKitCore                     	0x1b390b73c 0x1b2a29000 + 15607612
6   QuartzCore                    	0x1b5ea8494 0x1b5d57000 + 1381524
7   QuartzCore                    	0x1b5eae5ec 0x1b5d57000 + 1406444
8   QuartzCore                    	0x1b5eb9128 0x1b5d57000 + 1450280
9   QuartzCore                    	0x1b5e01b44 0x1b5d57000 + 699204
10  QuartzCore                    	0x1b5e2b4e4 0x1b5d57000 + 869604
11  QuartzCore                    	0x1b5e2c484 0x1b5d57000 + 873604
12  libsystem_pthread.dylib       	0x1af0bcf8c 0x1af0af000 + 57228
13  libsystem_pthread.dylib       	0x1af0b9df4 0x1af0af000 + 44532
14  libsystem_pthread.dylib       	0x1af0bae64 0x1af0af000 + 48740
15  libsystem_pthread.dylib       	0x1af0bac04 0x1af0af000 + 48132
16  libsystem_pthread.dylib       	0x1af0bd740 0x1af0af000 + 59200
Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0:
0   libsystem_kernel.dylib        	0x00000001af177198 0x1af173000 + 16792
1   libsystem_kernel.dylib        	0x00000001af17660c 0x1af173000 + 13836
2   CoreFoundation                	0x00000001af321328 0x1af279000 + 688936
3   CoreFoundation                	0x00000001af31c35c 0x1af279000 + 668508
4   CoreFoundation                	0x00000001af31bba8 0x1af279000 + 666536
5   GraphicsServices              	0x00000001b948b344 0x1b9488000 + 13124
6   UIKitCore                     	0x00000001b34573e4 0x1b2a29000 + 10675172
7   FunkyFundz                    	0x00000001024289e8 main + 35304 (AppDelegate.swift:15)
...

Full Error Log

Answered by car_service in 630745022

I am pretty sure I was experiencing an error related to having renamed some images in Assets.xcassets in Xcode.

This thread was very helpful:
https://developer.apple.com/forums/thread/106261

I say pretty sure because the app has been rejected again, but this time for a different reason :)

In terms of Xcode not properly symbolicating the error logs, I realized I hadn't updated iOS or Xcode to the most recent versions, so that may have been the cause.

Updated and onward!

Thank you very much for your help. I hope this thread helps someone else.

Boost

Answer 1

car_service OP

Sep ’20

Hello eskimo,

Thank you for your reply.

Following the instructions on the Adding Identifiable Symbol Names to a Crash Report page, I have been able to apply the appropriate .dSYM file to the crash report to identify lines associated with that particular .dSYM file (FunkyFundz.app.dSYM).

However, as you noted, the rest of the stack trace is not symbolicated. How can I go about symbolicating the rest of the crash report?

When I look in the dSYMs folder inside the .xcarchive I see .dSYM files associated with my app and my third party libraries.

However, in the stack trace I am trying to identify things like libsystem_kernel.dylib, CoreFoundation, and UIKitCore. I do not see .dSYM files for these. Should I be asking Xcode to generate and apply these somehow?

Thank you so much for your help and clarification. :)

Marvin

0

Answer 2

DTS Engineer OP

Apple

Sep ’20

Xcode’s Organizer should fill in symbols for system framework that it knows about. One problem here is that, if the crash came from a device / OS version combo that Xcode hasn’t seen, it won’t have the symbols for it.

Can you post a full crash report with your app’s symbols in place? The one in your original post seems to have been munged (it’s missing the first few lines).

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

0

Answer 3

car_service OP

Sep ’20

Accepted Answer

I am pretty sure I was experiencing an error related to having renamed some images in Assets.xcassets in Xcode.

This thread was very helpful:
https://developer.apple.com/forums/thread/106261

I say pretty sure because the app has been rejected again, but this time for a different reason :)

In terms of Xcode not properly symbolicating the error logs, I realized I hadn't updated iOS or Xcode to the most recent versions, so that may have been the cause.

Updated and onward!

Thank you very much for your help. I hope this thread helps someone else.

0