ios anaylize crash log? - ios

I have the following symbolized crash log. Or maybe something I missed?
Help please to understand what does it mean:
OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3591f628 0x3590e000 + 71208
1 libsystem_c.dylib 0x34accb1a nanosleep + 138
2 libsystem_c.dylib 0x34ad7608 sleep + 40
3 ReportCrash 0x001046f2 0xfc000 + 34546
4 ReportCrash 0x000fd474 0xfc000 + 5236

it is state of your app at the crash moment, can show you where crash was. In your case app crashed with Exception Type: EXC_CRASH (SIGKILL) in thread 0 and you can see stacks of functions of all active threads. If you want convert it to human readable view, you should use special programs like symbolicate , atos or dwarfdump.
More:
http://kevincupp.com/2011/05/12/symbolicating-ios-crash-logs.html
http://aplus.rs/ios-dev/guide-to-symbolicating-iphone-app-crash-logs-with-xcode-4-2/
(about atos i have link just in Russian)

It is very simple if you have the archive file in Xcode -> Widow ->Organizer and a corresponding crash log file.
Connect your device to mac
goto Xcode->Window-> devices
Click on your device on the left panel
Click on view device logs
Select the log you want to symbolicate. (OR) If you have a crash log file on your system then click on All logs option on the left panel and drag the log file into left panel section.
Right click on the selected log and click re-symbolicate
Done!!! ,

Related

App Crash (SIGABRT) only in AppStore Review, not in Sim or my Hardware

I recently updated a stable app which has been in the Store for over a year and well over a thousand downloads. Last updated 6/19. All fine.
This week I added a unique UserID to my Flurry start up in App Delegate and few extra flurry event calls in various view controllers to help track rare crashes (maybe 3 crashes reported in a year). App runs fine in Xcode Sim on a variety of devices, and in my real hardware both in debug and untethered. GIT compare confirms no other changes to codebase or XIBs, etc. Last compile for AppStore on Xcode 10.x, now 11.1
App Store review fails with crash on launch, they tried three times and sent crash logs. I removed some of the mods (but not yet the UserID in AppDelegate) and resubmitted: same result. First time I sent it in the crash report said they tested on a 3rd Gen iPad, so I asked them to try the second time on an iPhone, the next set of crash reports had the device code as XXX! They ran 13.1.2, I tested on 13.1.3 and on 12.1.4 all OK
Here's the problem(s)
1) I dont see how to symbolicate the crash reports. To do so, Xcode requires the App's binary and dSYM (I have those), I dont have the Flurry dSYM, and OS Symbols for the hardware/OS where the test ran. I dont have a 3rd gen iPad (iPad11,3) to plug in and get the symbols for Xcode. Is there an alternative path to symbolication in this circumstance.
2) I'm not sure that the symbols would help here anyway since it looks like the crash is deep in iOS frameworks (maybe abi, see below) after being called from my Main. I know that these kinds of launch crashes frequently occur when storyboards have a defect, but I cant see one and the app runs fine locally on new and old phones and old iPads. What would be my next steps when I can't replicate the crash (aside from removing the Flurry set UserID! (my next blind step!))?
UPDATE: I have now reverted all changes in the App back to last stable release in App Store (except a single bug fix where I needed to release a KVO Observer for users with old iOS). The reverted App still fails App Store review! The only diffs are in the storyboards where a bunch of Rects are different sizes because last open IB device was different than the last device in the repo from last submission. App runs fine on local sims and local hardware but still crashes on launch in App Store review.
{"app_name":"QueensDB","timestamp":"2019-10-30 15:28:10.12 -0700","app_version":"1.7","slice_uuid":"2133ecf9-943d-380e-9d2b-eb881e02a76f","adam_id":1369301260,"build_version":"2","share_with_app_devs":true,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 13.1.2 (17A860)","incident_id":"BB1B0B65-66BF-40B7-9017-7F8B14B57F58","name":"QueensDB"}
Incident Identifier: BB1B0B65-66BF-40B7-9017-7F8B14B57F58
CrashReporter Key: 1f7448b682620a373ff01cf8ae95a9238488a987
Hardware Model: iPad11,3
Process: QueensDB [90772]
Version: 2 (1.7)
AppStoreTools: 11A1002b
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Date/Time: 2019-10-30 15:28:09.6488 -0700
Launch Time: 2019-10-30 15:28:09.5818 -0700
OS Version: iPhone OS 13.1.2 (17A860)
Release Type: User
Baseband Version: n/a
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Application Specific Information:
abort() called
Last Exception Backtrace:
(0x184f6bc30 0x184c860c8 0x184e5b3ac 0x18897c810 0x18897cb2c 0x18855b700 0x18855b934 0x1884f6428 0x1889c59bc 0x1049975b8 0x104993ab4 0x188c935d8 0x18855b700 0x18855b934 0x1884f6428 0x188c928cc 0x1889c5b74 0x188920b94 0x188c935d8 0x18855b700 0x1884f6428 0x188c97784 0x18855b700 0x18855b934 0x1884f6428 0x188c926b0 0x188c952e8 0x18915a7d0 0x18915a660 0x1890007c4 0x189000d3c 0x188fff46c 0x1887a7710 0x188c537e8 0x1887a8248 0x1887a7c78 0x1887a8064 0x1887a78e8 0x1887ac098 0x188c6d214 0x188b80e90 0x188c6d1cc 0x1887abdb0 0x188c6d0b4 0x1887abc0c 0x188617630 0x1886160f4 0x188617360 0x188ffd91c 0x188ba2d7c 0x18a0d5014 0x18a0fbbd0 0x18a0e00f8 0x18a0fb864 0x184c1300c 0x184c15d50 0x18a122384 0x18a122030 0x18a12259c 0x184ee7260 0x184ee71b4 0x184ee6920 0x184ee17ec 0x184ee1098 0x18f04b534 0x1890017ac 0x10494a1c8 0x184d60f30)
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000184d56ef4 0x184d31000 + 155380
1 libsystem_pthread.dylib 0x0000000184c77d1c 0x184c75000 + 11548
2 libsystem_c.dylib 0x0000000184c07a54 0x184b91000 + 485972
3 libc++abi.dylib 0x0000000184d1e3c8 0x184d1d000 + 5064
4 libc++abi.dylib 0x0000000184d1e5c0 0x184d1d000 + 5568
5 libobjc.A.dylib 0x0000000184c863a8 0x184c80000 + 25512
6 libc++abi.dylib 0x0000000184d2b634 0x184d1d000 + 58932
7 libc++abi.dylib 0x0000000184d2b5c0 0x184d1d000 + 58816
8 libdispatch.dylib 0x0000000184c13020 0x184c10000 + 12320
9 libdispatch.dylib 0x0000000184c15d50 0x184c10000 + 23888
10 FrontBoardServices 0x000000018a122384 0x18a0c8000 + 369540
11 FrontBoardServices 0x000000018a122030 0x18a0c8000 + 368688
12 FrontBoardServices 0x000000018a12259c 0x18a0c8000 + 370076
13 CoreFoundation 0x0000000184ee7260 0x184e39000 + 713312
14 CoreFoundation 0x0000000184ee71b4 0x184e39000 + 713140
15 CoreFoundation 0x0000000184ee6920 0x184e39000 + 710944
16 CoreFoundation 0x0000000184ee17ec 0x184e39000 + 690156
17 CoreFoundation 0x0000000184ee1098 0x184e39000 + 688280
18 GraphicsServices 0x000000018f04b534 0x18f048000 + 13620
19 UIKitCore 0x00000001890017ac 0x1885d1000 + 10684332
20 QueensDB 0x000000010494a1c8 0x104944000 + 25032
21 libdyld.dylib 0x0000000184d60f30 0x184d60000 + 3888
Turns out, once the Store Reviewer send me a crash report on hardware/software version I could re-symbolicate, that the crash issue was my use of a SearchDisplayController which crashed while loading the initial view controller.
Interesting because the app runs fine on iOS 13.2 on my local hardware. Maybe there is a strictness setting I need to know about?
An Apple engineer provided the following information: The offending App must be thinned to reproduce the error: https://forums.developer.apple.com/thread/125520

EXC_BAD_ACCESS (SIGSEGV) when launching app from .ipa

I'm using a PDF reporting library, named PDFReporter, and I've got this weird crash when trying to generate a PDF. It happens only when I'm launching the app from an .ipa archive. It runs fine when I launch the app from Xcode.
Here's some of the trace I have from Xcode's Device logs :
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010
Triggered by Thread: 0
Filtered syslog: None found
Thread 0 name: main Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x0000000181501b90 objc_msgSend + 16
1 ExpoTouch 0x0000000100649e64 OrgOssPdfreporterEngineXmlJRXmlDigesterFactory_setComponentsInternalEntityResourcesWithOrgOssPdfreporterEngineXmlJRXmlDigester_
+ 72
2 ExpoTouch 0x000000010064a054 OrgOssPdfreporterEngineXmlJRXmlDigesterFactory_createDigester + 136
3 ExpoTouch 0x00000001006849d4 OrgOssPdfreporterEngineXmlJRXmlLoader_load__WithJavaIoInputStream_ + 140
4 ExpoTouch 0x000000010071062c +[ReportExporter loadReport:] + 72
So the question is : what's the difference between installing from Xcode and installing from an .ipa ? Am I missing a library in the .ipa ? If so, how could I know which one ?

Apple keeps rejecting my app

this was apple's message
14.3 Details
Your app enables the display of user-generated content but does not
have the required precautions in place.
Next Steps
It is necessary that you put all of the following precautions in
place:
Require that users agree to terms (EULA) and these terms must make it clear that there is no tolerance for objectionable content
Use moderators to flag and remove inappropriate content and offensive users
Users need a mechanism to flag objectionable content and report users generating this content
Users need a mechanism to block abusive users
Developer must act on objectionable content reports within 24 hours by removing the content and ejecting the user who provided the
offending content
Developer needs a method for ejecting users who violate the terms of the EULA
2.1 Details
During review, your app crashed on iPad running iOS 9.3.1 and iPhone
running iOS 9.3.1 when we:
Tap "..." On a post
This occurred when your app was used:
- Offline
- On Wi-Fi
- On cellular network
my app has a privacy policy & terms of service. also it has a more button which you can report things in it.. its the "..." button that crashes
the thing is it never crashed while trying it on multiple devices iPhones and iPads! i don't get why it keeps being rejected!
first time i sent it without terms of service but now i added it and resent it. but it got rejected again!
the crash log they sent is
Version: 1.1 (1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2016-04-14 19:54:17.17 -0700
Launch Time: 2016-04-14 19:53:55.55 -0700
OS Version: iOS 9.3.1 (13E238)
Report Version: 105
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Last Exception Backtrace:
(0x182c06e38 0x18226bf80 0x188695288 0x1880a9ec0 0x1880a7fd8 0x187ffafd8 0x188008990 0x187d3a4a4 0x182bbc7b0 0x182bba554 0x182bba984 0x182ae4d10 0x1843cc088 0x187db1f70 0x10011ccb0 0x1826828b8)
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001827a011c 0x182784000 + 114972
1 libsystem_pthread.dylib 0x000000018286cef8 0x182868000 + 20216
2 libsystem_c.dylib 0x0000000182711dac 0x1826b0000 + 400812
3 libc++abi.dylib 0x00000001822453f4 0x182244000 + 5108
4 libc++abi.dylib 0x0000000182261e98 0x182244000 + 122520
5 libobjc.A.dylib 0x000000018226c248 0x182264000 + 33352
6 libc++abi.dylib 0x000000018225ef44 0x182244000 + 110404
7 libc++abi.dylib 0x000000018225eb10 0x182244000 + 109328
8 libobjc.A.dylib 0x000000018226c120 0x182264000 + 33056
9 CoreFoundation 0x0000000182ae4db8 0x182adc000 + 36280
10 GraphicsServices 0x00000001843cc088 0x1843c0000 + 49288
11 UIKit 0x0000000187db1f70 0x187d34000 + 515952
12 iFandoms 0x000000010011ccb0 0x1000c0000 + 380080
13 libdyld.dylib 0x00000001826828b8 0x182680000 + 10424
this is just a part of it.. still it never crashed while i was testing it! please help me! my mind is gonna explode!
Ok so it turns out its a slight problem with the alert controller.. added some code and it worked!

Application only crashes on start when run on TestFlight

Currently I have an iOS app which I plan to release for beta testing. My problem is that the app will not run as after 2 seconds or so after the app has shown the GameScene.swift SKScene, it crashes and it keeps on repeating.
I have compiled the app via Xcode 7.3 in both Release and Debug configurations. I have analysed the project, cleaned it, uninstalled it, reinstalled it, restored my device etc. But nothing changes. This unexpected crash only happens when the app is run via TestFlight. I will attach below the log from the crashes. I have tried to symbolicate the crash but it just shows up the original log file.
Incident Identifier: 408B1212-4AE8-42E2-905F-D4567D5030AD
CrashReporter Key: 4c7013cab29b9011557c3005550950488452cc04
Hardware Model: xxx
Process: Number Tap [2226]
Path: /private/var/containers/Bundle/Application/69833BAF-AD19-4FAF-BB95-E766A493D525/Number Tap.app/Number Tap
Identifier: com.flatboxstudio.numbertap
Version: 2 (1.0.1)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2016-03-29 18:44:31.31 -0700
Launch Time: 2016-03-29 18:44:31.31 -0700
OS Version: iOS 9.3 (13E233)
Report Version: 105
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000100046724
Triggered by Thread: 0
Filtered syslog:
None found
Breadcrumb Trail: (reverse chronological seconds)
0 GC Framework: startAuthenticationForExistingPrimaryPlayer
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 Number Tap 0x0000000100046724 0x10000c000 + 239396
1 libdispatch.dylib 0x000000018200d4bc 0x18200c000 + 5308
2 libdispatch.dylib 0x000000018200d47c 0x18200c000 + 5244
3 libdispatch.dylib 0x0000000182012b84 0x18200c000 + 27524
4 CoreFoundation 0x0000000182578dd8 0x182498000 + 921048
5 CoreFoundation 0x0000000182576c40 0x182498000 + 912448
6 CoreFoundation 0x00000001824a0d10 0x182498000 + 36112
7 GraphicsServices 0x0000000183d88088 0x183d7c000 + 49288
8 UIKit 0x000000018776df70 0x1876f0000 + 515952
9 Number Tap 0x0000000100046bdc 0x10000c000 + 240604
10 libdyld.dylib 0x000000018203e8b8 0x18203c000 + 10424
Activity ID: 0x0000000000043e33
Activity Name: starting resolver activity
Activity Image Path: /usr/lib/system/libsystem_network.dylib
Activity Image UUID: A1D92752-ABF1-3834-9EBB-FE35E00EB642
Activity Offset: 0x0003333c
Activity Running Time: 0.468516 sec
Trace Messages (reverse chronological seconds):
0.292098 GameCenterFoundation 0x000000019066a20c authenticateWithCompletionHandler:Username and Password passed in. GKDaemonProxy to authenticate player
0.296164 CFNetwork 0x0000000204da9da8 Format not found
0.300431 CFNetwork 0x0000000204da9da8 Format not found
0.301584 CFNetwork 0x0000000204da9da8 Format not found
0.301623 CFNetwork 0x0000000182c493a8 TCP Conn 0x146553ea0 started
0.305076 CFNetwork 0x0000000182ca3ce8 Creating default cookie storage with default identifier
0.305077 CFNetwork 0x0000000182ca3cb4 Faulting in CFHTTPCookieStorage singleton
0.305077 CFNetwork 0x0000000182cf5e44 Faulting in NSHTTPCookieStorage singleton
I removed some of the log as I felt it may be unimportant. I have read apples guide on resolving this but still not resolved.I will be truly grateful if anybody could help me out. If you need any extra code, logs or information don't hesitate to ask. (The whole log was quite long so I cropped some information out.)

App Review has rejected my app: EXC_CRASH (SIGABRT)

We testing my app with iPhone 6s/iPhone 6/iPhone 5, no bugs and crash report, but when we submit to iTunesConnect, the App Review team has rejected my app, they said this app crashed on launch.
We can not reproduce this crash, I have no idea what the crash log below means. I would be really happy if anybody could explain me what this crash log could relate to and how I could solve it. Many many thanks to all those who are willing to help others.
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Filtered syslog:
2015-02-05 06:00:28.268 chuanBang[993]: <Error> assertion failed: 12B411: libxpc.dylib + 51955 [04694BEB-256F-3132-A00F-0C82B79BC689]: 0x7d
2015-02-05 06:00:29.105 chuanBang[993]: <Error> SecTrustEvaluate [leaf AnchorTrusted]
2015-02-05 06:00:29.517 chuanBang[993]: <Error> CoreLocation: Could not get ideal gyro update interval, assuming 0.005000 s
2015-02-05 06:00:30.615 chuanBang[993]: <Warning> Attempting to badge the application icon but haven't received permission from the user to badge the application
2015-02-05 06:00:30.619 chuanBang[993]: <Warning> 请求失败了
2015-02-05 06:00:30.623 chuanBang[993]: <Warning> 请求失败了
Last Exception Backtrace:
(0x26988d62 0x342bfc72 0x26988ca8 0x2c3084 0x3499b096 0x349a0d0e 0x348c0934 0x33acdbb8 0x33ae4e30 0x33ae48b4 0x342bfdba 0x2689aa18 0x2689a78e 0x2dd4c04c 0x29e8c97c 0x1b2a1a 0x3485baaa)
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x34920dfc 0x3490c000 + 85500
1 libsystem_pthread.dylib 0x349a0d0e 0x3499d000 + 15630
2 libsystem_c.dylib 0x348c0934 0x34877000 + 301364
3 libc++abi.dylib 0x33acdbb8 0x33acd000 + 3000
4 libc++abi.dylib 0x33ae4e30 0x33acd000 + 97840
5 libc++abi.dylib 0x33ae4ee6 0x33acd000 + 98022
6 libc++abi.dylib 0x33ae4b9c 0x33acd000 + 97180
7 libc++abi.dylib 0x33ae4e44 0x33acd000 + 97860
8 libc++abi.dylib 0x33ae48b4 0x33acd000 + 96436
9 libobjc.A.dylib 0x342bfdba 0x342b9000 + 28090
10 CoreFoundation 0x2689aa18 0x26881000 + 104984
11 CoreFoundation 0x2689a78e 0x26881000 + 104334
12 GraphicsServices 0x2dd4c04c 0x2dd43000 + 36940
13 UIKit 0x29e8c97c 0x29e1e000 + 452988
14 chuanBang 0x001b2a1a 0xad000 + 1071642
15 libdyld.dylib 0x3485baac 0x3485a000 + 6828
The crash log itself is not useful. I suggest integrating a crash reporting SDK into your app and when a crash does happen, it will give you a lot more info than you're currently getting.
Some crash reporters to look over:
Crashlytics
HockeyApp
Once you have one of these integrated into your app, submit the app again to Apple (If you cannot reproduce the error) and if it crashes their side, you'll have a much better idea where the issue is.
I think whenever you are testing your app at that time you always allow for Notification permission Popup & Location service permission popup.
Please try by click "Don't allow" when these popup are show.

Resources