I've read numerous threads on stackoverflow and on apple site and I still cannot get basics to work. I make a debug build of my app, I install it on my phone, this build intentionally crashes. I run this app while not connected with Xcode debugger. The app crashes, how do I see now function names and line numbers of the crash backtrace?
I tried to open devices windows in Xcode and there Iviewed the log, I see my app crashlog, I see that there were multiple function calls in my code before it crashed, but all of them are shown as hex addresses and not actually symbolicated. What do I need to do to make it work?
Open Project Settings. Go to your Target and set the Debug Information Format to DWARF with dSYM File for Debug. Do the same for the Project
Project:
Target:
Xcode will symbolicate the crash report, which can take a few seconds, only if you still have the matching symbols of the build that triggered the crash. If the symbol exists simply wait a bit and the crash report will update.
If you in the meantime changed some code and triggered a new build, then the build and symbol files will be overwritten and get a new UUID (per CPU architecture). That UUID is part of the crash report (Binary Images section) and used to find the matching symbol file on your Mac. If that isn't found, then symbolication can not work.
Could it be you are using an invalid character in your project name?
I had this same problem with seeing the hex and not the actual function names. Turns out the issue was a unicode character in my Apps name "➕". I removed it and then the subsequent crash logs in xcode would show the function calls correctly.
Any solution for this. I am having exactly this problem. I build, run it on my iPad, stop execution, and then manually start the app on the iPad. It crashes, I go to the Device Logs, and the crash is there but it won't symbolicate:
0 CoreFoundation 0x1b0d035ac __exceptionPreprocess + 220
1 libobjc.A.dylib 0x1c4d7d42c objc_exception_throw + 59
2 CoreFoundation 0x1b0c0c1b4 +[NSException raise:format:arguments:] + 99
3 Foundation 0x1b1f6a7bc -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 131
4 xxxxxxxxxxxxxxx 0x102f6c2d4 0x102f64000 + 33492
5 xxxxxxxxxxxxxxx 0x102f6c23c 0x102f64000 + 33340
6 xxxxxxxxxxxxxxx 0x102f76754 0x102f64000 + 75604
7 xxxxxxxxxxxxxxx 0x102f764ac 0x102f64000 + 74924
8 xxxxxxxxxxxxxxx 0x102f76f40 0x102f64000 + 77632
9 xxxxxxxxxxxxxxx 0x102f83fa0 0x102f64000 + 130976
There are no Unicode characters in my app name (which isn't really xxxxxxx).
Related
I am noticing it from my last few build, crashlytics is not sending the proper crash reports...
In crash reports i can not debug on which class the crash occured..
Although I have tried uploading DSYM manually also and using fabric also, I do have followed all the instructions on their website..
I have also tried by uploading DSYM by downloading from itunesconnect but not nothing gives proper crash log
Sample Crash report
Fatal Exception: NSRangeException
0 CoreFoundation 0x18cbcefe0 __exceptionPreprocess
1 libobjc.A.dylib 0x18b630538 objc_exception_throw
2 CoreFoundation 0x18caad200 -[__NSArrayM removeObjectAtIndex:]
3 MyApp 0x1001a3550 _hidden#4208_ (__hidden#4311_:498)
4 MyApp 0x10012c008 _hidden#1377_ (__hidden#1463_:318)
5 MyApp 0x10012f888 _hidden#1403_ (__hidden#1463_:753)
6 MyApp 0x100132448 _hidden#1497_ (__hidden#1511_:352)
7 MyApp 0x1001dc1b8 _hidden#5257_ (__hidden#5321_:209)
8 Foundation 0x18d6c24cc __NSThreadPerformPerform
9 CoreFoundation 0x18cb7d42c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
10 CoreFoundation 0x18cb7cd9c __CFRunLoopDoSources0
11 CoreFoundation 0x18cb7a9a8 __CFRunLoopRun
12 CoreFoundation 0x18caaada4 CFRunLoopRunSpecific
13 GraphicsServices 0x18e514074 GSEventRunModal
14 UIKit 0x192d65058 UIApplicationMain
15 MyApp 0x10018b9cc main (__hidden#3728_:14)
16 libdyld.dylib 0x18bab959c start
Why it is _hidden#4208??
Try this
Goto to Build Settings
then goto Build Options
In build options goto Debug Information Format
and Change Debug's DWARF to DWARF with DSYM File.
Now again follow Fabric crashlytics steps and you will definitely get the proper crash report.
Refer below screenshot
Please go through this Matt's answer on Xcode Bitcode, Include Symbols settings effect on dSYM generation
I've not tried it, but I think by following the guidelines mentioned in Matt's answer you can resolve your query.
My issue was, I was creating the build using command line tools and no bitcode flag was used that time for it. so it was giving improper crash reports to me.
Now I include bitcode symbols in my IPA and then after uploading it to appstoreconnect.apple.com if I download the dsym's for my IPA and upload it to crashlytisc's missing dsym section I do get all proper crash reports.
Note : I Downloaded the DSYM from the build uploaded to appstoreconnect, as that DSYM includes symbols and only that solved my issue.
finally find exact solution set Enable bitCode as a No in build setting
My app crash on start up, on splash screen. After it crashes, double click home button, and I find that it is in "app gallery", just like as if it went to the background. Click it, splash window came again and this time, it launch normally. This very strange.
I've got the crash log, but I lost the dSYM file for some reason, so I can't exactly locate the bug. The crash log is just like this:
(yes, only one thread in crash log; there should be many in fact.)
0 CoreFoundation 0x0000000182538f60 <redacted> + 148
1 libobjc.A.dylib 0x0000000197087f80 objc_exception_throw + 56
2 CoreFoundation 0x0000000182538e90 <redacted> + 0
3 stockmap-ios 0x00000001005d6fc4 stockmap-ios + 5156804
4 libsystem_platform.dylib 0x0000000197ab593c _sigtramp + 52
5 stockmap-ios 0x00000001003fa7ec stockmap-ios + 3205100
Another thing make me upset is that, I can only reproduce this crash on production mode (after build to .ipa), but I'm not able to do this on development mode. That makes me crazy... As you know I lack dSYM so the crash log is to some extent useless.
For my code, What are the differences between this two modes?
env info:
os: ios 9
device: at least, happens on Ipad2, Iphone6, Iphone6s. unknow about others.
I have an app which occasionally kicks users out after they've logged in and had it minimized for a few hours. It happens randomly with no preference for a specific device or os version. Here's the bugsense crash log
Error Message
data parameter is nil
Where
0x84000 +
Short Stacktrace
0 CoreFoundation 0x2e7cee83 + 130
1 libobjc.A.dylib 0x38b2b6c7 objc_exception_throw + 38
2 CoreFoundation 0x2e7cedc5 + 0
3 Foundation 0x2f156be7 + 66
4 MEMetrics 0x0009820d 0x84000 + 82445
5 Foundation 0x2f10947f + 54
Affected App Versions
2.0
Affected SDKs
7.0.4
Details (last occurence of error)
OS iOS 7.0.4
App Version 2.0
Device iPhone5,3
Country US
wifi_on 1
user_id user6#test.com
locale en_US
sdk_version 3.4
mobile_net_on 0
jailbreak 0
log_data {u'ms_from_start': 42804}
internal_version 2.0
carrier Verizon
build_uuid 5310A8F9-6F2B-3D2D-B7E8-9C5F9621FF3C
gps_on 1
execname MEMetrics
It seems to appear in no specific file.
You can make sense of these lines by uploading DSYM files in the Bugsense settings for a project.
Try going to a Project then Settings -> DSYMs (Here it explains how
you should zip and upload a DSYM file from an xarchive)
These are symbol definition files that help a crash report generator understand the lines of code that correspond to the information coded in that report. Upload latest DSym files each time you upload a binary for distribution or to app store (At least that is what I do, if someone knows of a better way or frequency on which we should upload these files please let us know)
I have a problem in understanding some things about these two crash reports that I get from Apple:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x617401fa
Crashed Thread: 0
0 app 0x0017c0ca Json::parse(int, JSON_value_struct const*) + 378
1 app 0x0017bf46 Json::parse(void*, int, JSON_value_struct const*) + 2
2 app 0x001302d2 JSON_parser_char + 2070
3 app 0x0017bb58 Json::parse(std::string const&) + 356
4 app 0x0008e682 NotificationData::ProcessNotifications(std::vector<UserEvent, std::allocator<UserEvent> >&) + 1062
5 app 0x00106aea SMS::CheckNotifications() + 106
6 app 0x001073dc SMS::update(Rex::TimeData const&) + 936
7 app 0x00192c7e SceneManager::updateTick(TimeData const&) + 314
8 app 0x001685ae Core::onRender(TimeData const&) + 522
and
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xffff0202
Crashed Thread: 0
0 app 0x0017c0ca 0x1000 + 1552586
1 app 0x0017bf46 0x1000 + 1552198
2 app 0x001302d2 0x1000 + 1241810
3 app 0x0017bb58 0x1000 + 1551192
4 app 0x0008e682 0x1000 + 579202
5 app 0x00106aea 0x1000 + 1071850
6 app 0x001073dc 0x1000 + 1074140
7 app 0x00192c7e 0x1000 + 1645694
8 app 0x001685ae 0x1000 + 1471918
Some facts first: the first is said to occur 40% of the time and the second time 35%. If this is true it's quite a good thing for me.
My reasoning based upon what I read about this stuff is that they are one and the same because the memory adresses of the functions are exactly the same, just the KERN_INVALID_ADDRESS at 0x617401fa and KERN_INVALID_ADDRESS at 0xffff0202 differ, which would be expected because the function was writting some corrupt file on disk
My first question is why do the crash reports sometime come symbolicated (or partially symbolicated) and other times not? (I just got into analyzing them and our build system wasn't saving the dSYM files generated for each build so I can't do much thing about symbolicating the second one)
The second one is how is it possible for a crash report to come symbolicated from the user? As I looked into the project , the settings for the released build are like this: the GCC_GENERATE_DEBUGGING_SYMBOLS is set to NO for ALL_BUILDS and and the target application level debug_information is set to dwarf with dSYM file and generate debug symbols is set to No. ( Side question: When it is built with these settings there is no dSYM generate but if I magically set the GCC_GENERATE_DEBUGGING_SYMBOLS to true from cMake(...) the dSYM is generated. As I read target level settings override build level settings)
Sorry for the long post, it's my first one.
Regarding the facts: it is 40% of the crashes that iTunes gets! That is by far not all crashes your app has. iTunes Connect only shows crashes from devices, where the user did approve sending anonymous usage data when setting up the device (since iOS 5 can be changed deep in the settings app later on). And only a fraction of users enable that, since they don't want to be tracked. On systems pre iOS5 crash reports are also only send once the device gets synced with iTunes.
So in a nutshell: Crash Reports on iTunes Connect do not give you a real view on crash reports. Here an example blog post about this fact from the Camera+ developers: http://taptaptap.com/blog/cameraplus-2-3-1-available-attack-of-the-crashinator/
Those two crash reports are identical, you are correct.
Question 1: All crash reports on the device are send to Apple not symbolicated. The symbolication happens on Apple's servers. And since they still get a damn lot of crash reports (even though only a fraction of what really happens) they only symbolicate 1 report per group to reduce load on their servers.
The symbolication of the second one would show the same result as the first one, since the memory addresses are identical.
Question 2: Apple uses the symbols from the app binary if they are not stripped from it. They don't use the dSYM nor do they have or want it. Disadvantage of this way: you don't get line numbers and the binary executable is 30-50% larger. The relevant build setting is COPY_PHASE_STRIP. I assume that is set to NO in your case.
Regarding settings level: select the project in Xcode, then the target, View the build settings not as Combined but as Levels. The value on the far left (Resolved column) is the one being used. If you are using build settings in .xcconfig files, they are usually set per build configuration on project level, target overwrites these if set differently.
I am beginning to receive crash reports from my iOS app via BugSense. I have included the debug symbols in my app and an getting info on the errors, eg. "* -[NSMutableArray objectAtIndex:]: index 0 beyond bounds for empty array" and also stacktraces such as:
Full Stacktrace
0 CoreFoundation __exceptionPreprocess 114
1 libobjc.A.dylib objc_exception_throw 24
2 CoreFoundation -[__NSArrayM objectAtIndex:] 184
3 Myapp Myapp 738167
4 UIKit -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:] 662
5 UIKit -[UITableView _userSelectRowAtPendingSelectionIndexPath:] 130
6 Foundation __NSFireDelayedPerform 368
7 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ 14
8 CoreFoundation __CFRunLoopDoTimer 850
9 CoreFoundation __CFRunLoopRun 1088
10 CoreFoundation CFRunLoopRunSpecific 230
11 CoreFoundation CFRunLoopRunInMode 58
12 GraphicsServices GSEventRunModal 114
13 GraphicsServices GSEventRun 62
14 UIKit -[UIApplication _run] 404
15 UIKit UIApplicationMain 670
16 Myap p Myapp 11901
17 Myapp Myapp
However, I want to symbolicate the reports so that I can pinpoint exactly where the bugs are in my code. How can I take the report data from Bugsense and do this? Is there a way to download the "regular" crash report from BugSense and use that, or is the data they provide enough to work off of somehow? I know which version of the app that the reports are coming from so i know which binaries to symbolicate against.
BugSense works by getting the symbols on the device and posting them on the server, in a format similar to what you see in a crash log. BugSense gets the exception stacktrace and when it can't find one, the crashed thread stacktrace. For a variety of reasons, this isn't always perfect.
The stacktrace that you posted is partially symbolicated. It looks like BugSense has a problem getting the symbols in your own code.
If you have followed the usage guide to the letter, it could be a failing of the framework itself. atos should help you discover the exact method calls in your code.
Disclaimer: I write the code for BugSense-iOS.framework.
If you have a free BugSense account, it wont Symbolicate the crash reports for you. However you can pay $19/month to enable this feature. Alternatively you can try use this python script I wrote.
https://github.com/dr4ke616/Bugsense-Symbolicater
You could also try symbolicating with Crittercism. I've been using them for the past month and their symbolification system has been spot on.
Just had to go through this myself today. I found a tutorial on the Ray Wenderlich site:
http://www.raywenderlich.com/33669/overview-of-ios-crash-reporting-tools-part-1
I had been using Bugsense the wrong way (without symbolicate and breadcrumb >.<).
Note: breadcrumb is for the rather expensive version.
How to upload dSYM to Bugsense website to symbolicate stacktrace
Anyhow, from the tutorial, I found out I needed to upload the dSYM folder as a zipped file to Bugsense.
This folder essentially allows the raw stacktrace to symbolicate with which function calls caused the crash, also showing line number.
When you do an archive, you get the archive file in Window > Organizer.
To get the dSYM file, you need to:
Right click the archive > Show In Finder from the Window > Organizer
screen.
Then right click the file > Show packaged contents, this will show you the dSYM folder.
Right click and zip that folder up.
Login to your bugsense account, look for your app, go to the settings page and there should be a tab on the left called "dSYM". Tap on that and then press the Browse & Upload button to upload your dSYM.
Now you can go to each of your bug and press the "symbolicate" button, this will turn all those nasty:
0000x1aeaf390a
crash messages to something like:
MyViewController:m110, [MyViewController objectAtIndex:17] out of bounds
You need to upload the respective dSYM zipped file for the respective archive that you generated everytime you generate a new bundle version of your app.
Otherwise, if you try to use Bugsense without this dSYM, you'll get a useless stacktrace.
Hope that benefits anyone in the future. Good luck!