I have an iPhone app which works great most of the time, but one time when I downloaded it from the AppStore, I continually got the below error. This error continued until I deleted and reinstalled the application. Note that it did not run correct even once before starting this crash, and this crash happened almost at the exact time I touched the icon. Its strange, because it would not even have time to change any configuration files. Also, as you can see the crash occurred outside of my code. Any information would be appreciated.
Incident Identifier: F1333682-4BC7-44D7-9D7F-485EB7875780
CrashReporter Key: 657dffd01725b5b4b119912904a52134bc517824
Hardware Model: iPhone2,1
Process: iGunPro [9297]
Path: /var/mobile/Applications/A97E28F0-A0A1-45A2-A966-8EB0DC359945/iGunPro.app/iGunPro
Identifier: iGunPro
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2011-12-02 02:26:34.590 -0500
OS Version: iPhone OS 5.0.1 (9A405)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3744532c 0x37434000 + 70444
1 libsystem_c.dylib 0x3635cf54 0x3630f000 + 319316
2 libsystem_c.dylib 0x36355fe4 0x3630f000 + 290788
3 GraphicsServices 0x321c6444 0x321c2000 + 17476
4 GraphicsServices 0x321c6e84 0x321c2000 + 20100
5 UIKit 0x36fc6520 0x36f95000 + 202016
6 iGunPro 0x00006d20 main (main.m:53)
7 iGunPro 0x0000374c start + 44
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x374353b4 0x37434000 + 5044
1 libdispatch.dylib 0x36697e78 0x3668b000 + 52856
2 libdispatch.dylib 0x36697b96 0x3668b000 + 52118
Thread 2:
0 libsystem_kernel.dylib 0x37445cd4 0x37434000 + 72916
1 libsystem_c.dylib 0x3631930a 0x3630f000 + 41738
2 libsystem_c.dylib 0x3631909c 0x3630f000 + 41116
Thread 3:
0 libsystem_kernel.dylib 0x37445cd4 0x37434000 + 72916
1 libsystem_c.dylib 0x3631930a 0x3630f000 + 41738
2 libsystem_c.dylib 0x3631909c 0x3630f000 + 41116
Thread 4 name: WebThread
Thread 4:
0 libsystem_kernel.dylib 0x37435010 0x37434000 + 4112
1 libsystem_kernel.dylib 0x37435206 0x37434000 + 4614
2 CoreFoundation 0x33dee41c 0x33d61000 + 578588
3 CoreFoundation 0x33ded154 0x33d61000 + 573780
4 CoreFoundation 0x33d704d6 0x33d61000 + 62678
5 CoreFoundation 0x33d7039e 0x33d61000 + 62366
6 WebCore 0x3483f128 0x34797000 + 688424
7 libsystem_c.dylib 0x3631ec16 0x3630f000 + 64534
8 libsystem_c.dylib 0x3631ead0 0x3630f000 + 64208
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x00000000
r4: 0x00000006 r5: 0x3f37ece8 r6: 0x3f52ffe0 r7: 0x2fdffc84
r8: 0x2fdffd60 r9: 0x00272000 r10: 0x00000001 r11: 0x00000000
ip: 0x00000148 sp: 0x2fdffc78 lr: 0x3635cf5b pc: 0x3744532c
cpsr: 0x00000010`
`
This looks as though there is some process running in a background thread that shouldn't. For example, if you attempted some sort of UI manipulation using grand central dispatch that is NOT on the main queue, you might see this behavior. Another example, if you are using core data and you are sharing a managed object context across threads, you may see this behavior.
Something else to consider, there is probably a variable that is being overreleased.
Related
I got crash if application is not in background state and then click on notification. There is no memory leak and set architectures standard (armv6,armv7,armv7s).also referred link
Springboard crash when app is restored from push notification from GameCenter
Any suggestion to find out solution.Thanks in Advance.
Device Log as below:
OS Version: iOS 6.1.3 (10B329)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000024
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libdispatch.dylib 0x3936b332 0x3936a000 + 4914
1 CropAndGuess 0x000a92c0 0xa1000 + 33472
2 CropAndGuess 0x000a6252 0xa1000 + 21074
3 CropAndGuess 0x000a551a 0xa1000 + 17690
4 UIKit 0x3313ead4 0x330db000 + 408276
5 UIKit 0x3313e65e 0x330db000 + 407134
6 UIKit 0x33136846 0x330db000 + 374854
7 UIKit 0x330dec34 0x330db000 + 15412
8 UIKit 0x330de6c8 0x330db000 + 14024
9 UIKit 0x330de116 0x330db000 + 12566
10 GraphicsServices 0x34dd05a0 0x34dca000 + 26016
11 CoreFoundation 0x312ab680 0x31214000 + 620160
12 CoreFoundation 0x312aaee4 0x31214000 + 618212
13 CoreFoundation 0x312a9cb2 0x31214000 + 613554
14 CoreFoundation 0x3121ceb8 0x31214000 + 36536
15 CoreFoundation 0x3121cd44 0x31214000 + 36164
16 UIKit 0x33135480 0x330db000 + 369792
17 UIKit 0x331322fc 0x330db000 + 357116
18 CropAndGuess 0x000a3bbc 0xa1000 + 11196
19 CropAndGuess 0x000a3b54 0xa1000 + 11092
Thread 1:
0 libsystem_kernel.dylib 0x39452d98 0x39441000 + 73112
1 libsystem_c.dylib 0x393a0cf6 0x3939a000 + 27894
2 libsystem_c.dylib 0x393a0a12 0x3939a000 + 27154
3 libsystem_c.dylib 0x393a08a0 0x3939a000 + 26784
Thread 2 name: Dispatch queue: com.apple.libdispatch-manager
Thread 2:
0 libsystem_kernel.dylib 0x39442648 0x39441000 + 5704
1 libdispatch.dylib 0x3937b4ec 0x3936a000 + 70892
2 libdispatch.dylib 0x3936ddf4 0x3936a000 + 15860
Thread 3:
0 libsystem_kernel.dylib 0x39452d98 0x39441000 + 73112
1 libsystem_c.dylib 0x393a0cf6 0x3939a000 + 27894
2 libsystem_c.dylib 0x393a0a12 0x3939a000 + 27154
3 libsystem_c.dylib 0x393a08a0 0x3939a000 + 26784
Thread 4 name: WebThread
Thread 4:
0 libsystem_kernel.dylib 0x39441eb4 0x39441000 + 3764
1 libsystem_kernel.dylib 0x39442048 0x39441000 + 4168
2 CoreFoundation 0x312ab040 0x31214000 + 618560
3 CoreFoundation 0x312a9d9e 0x31214000 + 613790
4 CoreFoundation 0x3121ceb8 0x31214000 + 36536
5 CoreFoundation 0x3121cd44 0x31214000 + 36164
6 WebCore 0x3720a500 0x37200000 + 42240
7 libsystem_c.dylib 0x393ab30e 0x3939a000 + 70414
8 libsystem_c.dylib 0x393ab1d4 0x3939a000 + 70100
Thread 0 crashed with ARM Thread State (32-bit):
r0: 0x00000000 r1: 0x1fdaab50 r2: 0x3936c115 r3: 0x1fdaab50
r4: 0x3aefd06c r5: 0x0015a854 r6: 0x00153828 r7: 0x2fd5e4e8
r8: 0x00000001 r9: 0x0000007f r10: 0x38f4f5a1 r11: 0x001538d4
ip: 0x3aefe7f4 sp: 0x2fd5e4b4 lr: 0x000a92c5 pc: 0x3936b332
cpsr: 0x20000030
It is really very strange for me as my app is working fine at debug mode & when tried by tester with release build RARELY it gives crash. What I have understood from console log & crash log is that somewhere UI is trying to update from secondary thread but NOT always.
At crash point my console log says,
MyApp[715] <Warning>: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.May 21 10:51:25
MyApp[715] <Warning>: bool _WebTryThreadLock(bool), 0x1e1dd280: Tried to obtain the web lock from a thread other than the main thread or the web thread. This may be a result of calling to UIKit from a secondary thread. Crashing now...May 21 10:51:25
MyApp[715] <Notice>: 1 0x38b048f7 WebThreadLock
& device crash logs crash thread description & error type are as below
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xbbadbeef
Crashed Thread: 15
.
.
.
Thread 15 Crashed: 0
WebCore 0x38b03944_WebTryThreadLock(bool) + 164 1
WebCore 0x38b048f2 WebThreadLock + 62 2
UIKit 0x374424f6 -[UIWebTiledView layoutSubviews] + 38 3
UIKit 0x374424c6 -[UIWebDocumentView layoutSubviews] + 106 4
UIKit 0x373bb7fe -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 254 5
QuartzCore 0x30e92d5e -[CALayer layoutSublayers] + 210 6
QuartzCore 0x30e928fc CA::Layer::layout_if_needed(CA::Transaction*) + 456 7
QuartzCore 0x30e93830 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 12 8
QuartzCore 0x30e93216 CA::Context::commit_transaction(CA::Transaction*) + 234 9
QuartzCore 0x30e93024 CA::Transaction::commit() + 312 10
QuartzCore 0x30ed9df6 CA::Transaction::release_thread(void*) + 166 11 libsystem_c.dylib 0x31150128 _pthread_tsd_cleanup + 172 12
libsystem_c.dylib 0x3114fdfe _pthread_exit + 114 13
libsystem_c.dylib 0x31169160 pthread_exit + 24 14
Foundation 0x358bf226 +[NSThread exit] + 6 15
Foundation 0x35936696 __NSThread__main__ + 998 16
libsystem_c.dylib 0x3115d30e _pthread_start + 306 17
libsystem_c.dylib 0x3115d1d4 thread_start + 4
Thread 15 crashed with ARM Thread State (32-bit): r0: 0xbbadbeef r1: 0x00000000 r2: 0x030ba404 r3: 0x00000001 r4: 0x1e1dd280 r5: 0x3b4cacc0 r6: 0x00000000 r7: 0x030baa74 r8: 0x00000028 r9: 0x00006200 r10: 0x00000000 r11: 0x030bbc70 ip: 0x3b4061e0 sp: 0x030baa6c lr: 0x38b0393b pc: 0x38b03944 cpsr: 0x60000030
I am not very sure about this fix as i have not yet reproduced it at my end. If anyone at-least could help me out for reproducing then it would be great help :)
you do GUI changes in background thread but according to apple you are not changes in GUI in background thread...so use performSelectorOnMainThread to GUI change
This may be a result of calling to UIKit from a secondary thread.
Update the user interface on the main thread.In any of the case for doing UI updates in Separate thread reason will be invalid. One Option is Grand Central Dispatch as it do things in background threads and no crash at all.
Apple rejected our iphone app, showing that it crashed on iPad. We could not reproduce the crash on 3 different iPads and asked them to confirm. Apple came back saying that they produced the crash on iPhone 4 (although the log shows iPhone 3). We can not reproduce it...
They produce the crash by: Launch app. Select Let me look around
first. App crashes.
The log they sent us back seems to not show any of the apps own methods called:
ncident Identifier: 8B5E90DE-99FD-4279-B634-2C777209F2B3
CrashReporter Key: 6e9ccd0fcdc29915ebe22fb7376bd343cdcc252a
Hardware Model: iPhone3,1
Process: Snug [297]
Path: /var/mobile/Applications/DB3EFF00-7E5E-492A-9108-1341B6371B0D/Snug.app/Snug
Identifier: Snug
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-09-09 13:00:32.642 -0700
OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 6
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x319e7660 __semwait_signal_nocancel + 24
1 libsystem_c.dylib 0x3410b4da nanosleep$NOCANCEL + 118
2 libsystem_c.dylib 0x340dd3a0 usleep$NOCANCEL + 44
3 libsystem_c.dylib 0x340dd2b6 abort + 118
4 Snug 0x001f8760 uncaught_exception_handler + 12
5 CoreFoundation 0x37830950 __handleUncaughtException + 68
6 libobjc.A.dylib 0x3553533e _objc_terminate + 122
7 libc++abi.dylib 0x36f683be safe_handler_caller(void (*)()) + 70
8 libc++abi.dylib 0x36f6844a std::terminate() + 14
9 libc++abi.dylib 0x36f6981e __cxa_rethrow + 82
10 libobjc.A.dylib 0x355352a2 objc_exception_rethrow + 6
11 CoreFoundation 0x37786506 CFRunLoopRunSpecific + 398
12 CoreFoundation 0x37786366 CFRunLoopRunInMode + 98
13 GraphicsServices 0x33f45432 GSEventRunModal + 130
14 UIKit 0x31532cce UIApplicationMain + 1074
15 Snug 0x000f590c main (main.m:16)
16 Snug 0x000f58c0 start + 32
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x319d73a8 kevent + 24
1 libdispatch.dylib 0x3095cea4 _dispatch_mgr_invoke + 708
2 libdispatch.dylib 0x3095cbc2 _dispatch_mgr_thread + 30
Thread 2:
0 libsystem_kernel.dylib 0x319e7cd4 __workq_kernreturn + 8
1 libsystem_c.dylib 0x3409ff36 _pthread_wqthread + 610
2 libsystem_c.dylib 0x3409fcc8 start_wqthread + 0
Thread 3:
0 libsystem_kernel.dylib 0x319e7cd4 __workq_kernreturn + 8
1 libsystem_c.dylib 0x3409ff36 _pthread_wqthread + 610
2 libsystem_c.dylib 0x3409fcc8 start_wqthread + 0
Thread 4 name: WebThread
Thread 4:
0 libsystem_kernel.dylib 0x319d7004 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x319d71fa mach_msg + 50
2 CoreFoundation 0x378043ec __CFRunLoopServiceMachPort + 120
3 CoreFoundation 0x37803124 __CFRunLoopRun + 876
4 CoreFoundation 0x3778649e CFRunLoopRunSpecific + 294
5 CoreFoundation 0x37786366 CFRunLoopRunInMode + 98
6 WebCore 0x3312fc9c RunWebThread(void*) + 396
7 libsystem_c.dylib 0x340a572e _pthread_start + 314
8 libsystem_c.dylib 0x340a55e8 thread_start + 0
Thread 5 name: com.apple.NSURLConnectionLoader
Thread 5:
0 libsystem_kernel.dylib 0x319d7004 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x319d71fa mach_msg + 50
2 CoreFoundation 0x378043ec __CFRunLoopServiceMachPort + 120
3 CoreFoundation 0x37803124 __CFRunLoopRun + 876
4 CoreFoundation 0x3778649e CFRunLoopRunSpecific + 294
5 CoreFoundation 0x37786366 CFRunLoopRunInMode + 98
6 Foundation 0x38016bb2 +[NSURLConnection(Loader) _resourceLoadLoop:] + 302
7 Foundation 0x38016a7a -[NSThread main] + 66
8 Foundation 0x380aa58a __NSThread__main__ + 1042
9 libsystem_c.dylib 0x340a572e _pthread_start + 314
10 libsystem_c.dylib 0x340a55e8 thread_start + 0
Thread 6 Crashed:
0 libsystem_kernel.dylib 0x319e7cd4 __workq_kernreturn + 8
1 libsystem_c.dylib 0x3409ff36 _pthread_wqthread + 610
2 libsystem_c.dylib 0x3409fcc8 start_wqthread + 0
Thread 7:
0 libsystem_kernel.dylib 0x319e7cd4 __workq_kernreturn + 8
1 libsystem_c.dylib 0x3409ff36 _pthread_wqthread + 610
2 libsystem_c.dylib 0x3409fcc8 start_wqthread + 0
Thread 8:
0 libsystem_kernel.dylib 0x319e7cd4 __workq_kernreturn + 8
1 libsystem_c.dylib 0x3409ff36 _pthread_wqthread + 610
2 libsystem_c.dylib 0x3409fcc8 start_wqthread + 0
Thread 9 name: com.apple.CFSocket.private
Thread 9:
0 libsystem_kernel.dylib 0x319e7570 __select + 20
1 CoreFoundation 0x3780863a __CFSocketManager + 726
2 libsystem_c.dylib 0x340a572e _pthread_start + 314
3 libsystem_c.dylib 0x340a55e8 thread_start + 0
Thread 6 crashed with ARM Thread State:
r0: 0x00000004 r1: 0x00000000 r2: 0x00000000 r3: 0x00000000
r4: 0x0c8cc800 r5: 0x0036a08c r6: 0x04339000 r7: 0x04338fe0
r8: 0x3f29fd30 r9: 0x00000000 r10: 0x3f29fd50 r11: 0x00000000
ip: 0x00000170 sp: 0x04338fc0 lr: 0x3409ff3d pc: 0x319e7cd4
cpsr: 0x40000010
Can anyone enlighten us with this crash report?
UPDATE:
We nagged the app review team to send us the console trace, they did. In the trace it was evident that a call is being made to a String category method that does not exists.
The fault was that the particular category implementation file was not added to our release target. So everything worked perfectly but when the app was archived an implementation file was missing.
Unfortunately this log doesn't look like it'll be too useful - it just shows the main thread handling an exception that's being re-thrown from another thread; that thread has gone off to do something else at the time of the log.
You mention your suspicion about the RestKit loop and the possibility NSOperation is throwing the exception. That's possible and worth putting a check in (and crossing your fingers that it doesn't break something else...), but it's probably time to beg the app review team to give you better steps to reproduce. See if you can pin down what you all are doing differently. I wish I had a better answer for you, but I think exploring all you can about what you're doing in the background while in this part of the app and trying to figure out the missing steps to reproduce is going to be your best bet. Good luck!
The crash happened in Thread 0 at the top most Snug line 4
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x319e7660 __semwait_signal_nocancel + 24
1 libsystem_c.dylib 0x3410b4da nanosleep$NOCANCEL + 118
2 libsystem_c.dylib 0x340dd3a0 usleep$NOCANCEL + 44
3 libsystem_c.dylib 0x340dd2b6 abort + 118
4 Snug 0x001f8760 uncaught_exception_handler + 12
5 CoreFoundation 0x37830950 __handleUncaughtException + 68
6 libobjc.A.dylib 0x3553533e _objc_terminate + 122
7 libc++abi.dylib 0x36f683be safe_handler_caller(void (*)()) + 70
8 libc++abi.dylib 0x36f6844a std::terminate() + 14
9 libc++abi.dylib 0x36f6981e __cxa_rethrow + 82
10 libobjc.A.dylib 0x355352a2 objc_exception_rethrow + 6
11 CoreFoundation 0x37786506 CFRunLoopRunSpecific + 398
12 CoreFoundation 0x37786366 CFRunLoopRunInMode + 98
13 GraphicsServices 0x33f45432 GSEventRunModal + 130
14 UIKit 0x31532cce UIApplicationMain + 1074
15 Snug 0x000f590c main (main.m:16)
16 Snug 0x000f58c0 start + 32
There the app caused an exception which was not caught.
To symbolicate the report just drag it into xCode - you need to have the dSYM file for the reviewed version. Then xCode will show you the exact line where the problem occured. To get the dSym you need to "build and archive".
Also since the crash code is
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
the reason for the crash is a memory access problem. These kind of crash reports are generated in many cases where one tries to instert a nil object into an array or dictionary. (since the crash is in the main thread and not in Thread 6 as reported)
In your case I do not see any obvious insert, however I would check the logic starting in line 16 of your main file and all the subsequent. I would assume you are accessing an object which is not existent anymore at the time of this invokation.
You can analyze the crash report using the below
Steps to analyze crash report from apple:
Copy the release .app file which was pushed to the appstore, the .dSYM file that was created at the time of release and the crash report receive from APPLE into a FOLDER.
OPEN terminal application and go to the folder created above (using CD command)
atos -arch armv7 -o YOURAPP.app/YOURAPP MEMORY_LOCATION_OF_CRASH. The memory location should be the one at which the app crashed as per the report.
Ex: atos -arch armv7 -o 'app name.app'/'app name' 0x0003b508
This would show you the exact line, method name which resulted in crash.
Ex: [classname functionName:]; -510
Symbolicating IPA
if we use IPA for symbolicating - just rename the extention .ipa with .zip , extract it then we can get a Payload Folder which contain app. In this case we don't need .dSYM file.
Link for this Symbolicating iPhone App Crash Reports
My app was rejected, but I don't know what's the problem.
Rejected reason is:
We found that your app crashed on iPhone 4 running iOS 5.0.1, which is not in compliance with the App Store Review Guidelines.
Your app crashed on both Wi-Fi and cellular networks
when we:
1) Launch the app connected to a Wi-Fi or cellular network
2) The app crashes.
But, I test the my app withe iphone 4 running ios 5.0.1 which didn't come out crash like that, so I'm confused, plz help me, thanks a million.
Incident Identifier: AAA90ABE-B2F1-483A-97B8-2990DF83698C
CrashReporter Key: 52a7dd4ac386930f5f86a0b0e9b2de47158609a3
Hardware Model: iPhone3,1
Process: *****
Path: *******
Identifier: *****
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-01-26 17:51:05.914 -0800
OS Version: iPhone OS 5.0.1 (9A405)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x35fd832c 0x35fc7000 + 70444
1 libsystem_c.dylib 0x32ea1f54 0x32e54000 + 319316
2 libsystem_c.dylib 0x32e9afe4 0x32e54000 + 290788
3 libc++abi.dylib 0x334e4f64 0x334de000 + 28516
4 libc++abi.dylib 0x334e23ea 0x334de000 + 17386
5 libc++abi.dylib 0x334e244a 0x334de000 + 17482
6 libc++abi.dylib 0x334e381e 0x334de000 + 22558
7 libobjc.A.dylib 0x3430d22e 0x34304000 + 37422
8 CoreFoundation 0x3401353e 0x34004000 + 62782
9 CoreFoundation 0x3401339e 0x34004000 + 62366
10 GraphicsServices 0x30897fc6 0x30894000 + 16326
11 UIKit 0x3749473c 0x37463000 + 202556
12 *******（app's name） 0x00003e74 0x1000 + 11892
13 ******* 0x00003e2c 0x1000 + 11820
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x35fc83b4 0x35fc7000 + 5044
1 libdispatch.dylib 0x36cf2e78 0x36ce6000 + 52856
2 libdispatch.dylib 0x36cf2b96 0x36ce6000 + 52118
Thread 2 name: Dispatch queue: com.apple.root.default-priority
Thread 2:
0 DataDetectorsCore 0x37a54828 0x37a4e000 + 26664
1 DataDetectorsCore 0x37a5456c 0x37a4e000 + 25964
2 DataDetectorsCore 0x37a51b90 0x37a4e000 + 15248
3 DataDetectorsCore 0x37a520b8 0x37a4e000 + 16568
4 DataDetectorsCore 0x37a50da8 0x37a4e000 + 11688
5 DataDetectorsUI 0x34613db6 0x3460e000 + 23990
6 Foundation 0x35a2e39c 0x35a03000 + 177052
7 Foundation 0x35a9779c 0x35a03000 + 608156
8 libdispatch.dylib 0x36ce6d4e 0x36ce6000 + 3406
9 libdispatch.dylib 0x36cf279c 0x36ce6000 + 51100
10 libsystem_c.dylib 0x32e5e1c8 0x32e54000 + 41416
11 libsystem_c.dylib 0x32e5e09c 0x32e54000 + 41116
Thread 3 name: WebThread
Thread 3:
0 libsystem_kernel.dylib 0x35fc8010 0x35fc7000 + 4112
1 libsystem_kernel.dylib 0x35fc8206 0x35fc7000 + 4614
2 CoreFoundation 0x3409141c 0x34004000 + 578588
3 CoreFoundation 0x34090154 0x34004000 + 573780
4 CoreFoundation 0x340134d6 0x34004000 + 62678
5 CoreFoundation 0x3401339e 0x34004000 + 62366
6 WebCore 0x364e7128 0x3643f000 + 688424
7 libsystem_c.dylib 0x32e63c16 0x32e54000 + 64534
8 libsystem_c.dylib 0x32e63ad0 0x32e54000 + 64208
Thread 4:
0 libsystem_kernel.dylib 0x35fd8cd4 0x35fc7000 + 72916
1 libsystem_c.dylib 0x32e5e30a 0x32e54000 + 41738
2 libsystem_c.dylib 0x32e5e09c 0x32e54000 + 41116
Thread 5 name: com.apple.NSURLConnectionLoader
Thread 5:
0 libsystem_kernel.dylib 0x35fc8010 0x35fc7000 + 4112
1 libsystem_kernel.dylib 0x35fc8206 0x35fc7000 + 4614
2 CoreFoundation 0x3409141c 0x34004000 + 578588
3 CoreFoundation 0x34090154 0x34004000 + 573780
4 CoreFoundation 0x340134d6 0x34004000 + 62678
5 CoreFoundation 0x3401339e 0x34004000 + 62366
6 Foundation 0x35a13bc2 0x35a03000 + 68546
7 Foundation 0x35a13a8a 0x35a03000 + 68234
8 Foundation 0x35aa759a 0x35a03000 + 673178
9 libsystem_c.dylib 0x32e63c16 0x32e54000 + 64534
10 libsystem_c.dylib 0x32e63ad0 0x32e54000 + 64208
Thread 6:
0 libsystem_kernel.dylib 0x35fd8cd4 0x35fc7000 + 72916
1 libsystem_c.dylib 0x32e5e30a 0x32e54000 + 41738
2 libsystem_c.dylib 0x32e5e09c 0x32e54000 + 41116
Thread 7:
0 libsystem_kernel.dylib 0x35fd8cd4 0x35fc7000 + 72916
1 libsystem_c.dylib 0x32e5e30a 0x32e54000 + 41738
2 libsystem_c.dylib 0x32e5e09c 0x32e54000 + 41116
Thread 8 name: com.apple.CFSocket.private
Thread 8:
0 libsystem_kernel.dylib 0x35fd8570 0x35fc7000 + 71024
1 CoreFoundation 0x3409566a 0x34004000 + 595562
2 libsystem_c.dylib 0x32e63c16 0x32e54000 + 64534
3 libsystem_c.dylib 0x32e63ad0 0x32e54000 + 64208
Thread 9:
0 libsystem_kernel.dylib 0x35fd8cd4 0x35fc7000 + 72916
1 libsystem_c.dylib 0x32e5e30a 0x32e54000 + 41738
2 libsystem_c.dylib 0x32e5e09c 0x32e54000 + 41116
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x00000000
r4: 0x00000006 r5: 0x3e78bce8 r6: 0x00000002 r7: 0x2fdffb1c
r8: 0x3f448d6c r9: 0x334e5a32 r10: 0x00000000 r11: 0x3f448d6c
ip: 0x00000148 sp: 0x2fdffb10 lr: 0x32ea1f5b pc: 0x35fd832c
cpsr: 0x00070010
1) If you are not using ARC, convert your project to ARC. That will make crashes like this much less likley.
2) To see where in your code you crashed, you need to desymbolicate the crash log so it will show you where in your code the call that crashed came from. Try following these instructions:
Symbolicating iPhone App Crash Reports
According to EveryMac, iPhone3,1 is the GSM model of the iPhone 4.
Did you test with a GSM model, or a CDMA model? This crash may only happen with the GSM model.
Here is the crash report, the only entry of my app are the last two lines of the Thread 0 that crashed. Is it possible to get to the bottom of this crash?
CrashReporter Key: 4cc3bf614179cfc630ec151430177d3d47175000
Hardware Model: iPad2,1
Process: MyApp [750]
Path: /var/mobile/Applications/96D92A43-EA51-4988-88ED-AFDF005995DF/MyApp.app/MyApp
Identifier: MyApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2011-11-20 09:19:34.803 -0600
OS Version: iPhone OS 5.0.1 (9A405)
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Last Exception Backtrace:
(0x37ee18bf 0x37a2d1e5 0x37ee17b9 0x37ee17db 0x35178cab 0x15b53 0x12ded 0x319c27ff 0x2c4b 0x3520550f 0x37ead577 0x37e390cf 0x351793fb 0xb66d 0x31a3c565 0x31ab4ce7 0x35211943 0x37eb5a63 0x37eb56c9 0x37eb429f 0x37e374dd 0x37e373a5 0x37c0efcd 0x319b7743 0x2585 0x2550)
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3054232c 0x30531000 + 70444
1 libsystem_c.dylib 0x379e3f54 0x37996000 + 319316
2 libsystem_c.dylib 0x379dcfe4 0x37996000 + 290788
3 libc++abi.dylib 0x3043ef64 0x30438000 + 28516
4 libc++abi.dylib 0x3043c346 0x30438000 + 17222
5 libobjc.A.dylib 0x37a2d2dc 0x37a24000 + 37596
6 libc++abi.dylib 0x3043c3be 0x30438000 + 17342
7 libc++abi.dylib 0x3043c44a 0x30438000 + 17482
8 libc++abi.dylib 0x3043d81e 0x30438000 + 22558
9 libobjc.A.dylib 0x37a2d22e 0x37a24000 + 37422
10 CoreFoundation 0x37e3753e 0x37e28000 + 62782
11 CoreFoundation 0x37e3739e 0x37e28000 + 62366
12 GraphicsServices 0x37c0efc6 0x37c0b000 + 16326
13 UIKit 0x319b773c 0x31986000 + 202556
14 MyApp 0x0000257e main (main.m:14)
15 MyApp 0x00002548 start + 32
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x305323b4 0x30531000 + 5044
1 libdispatch.dylib 0x30a9df74 0x30a9a000 + 16244
2 libdispatch.dylib 0x30a9dc92 0x30a9a000 + 15506
Thread 2:
0 libsystem_kernel.dylib 0x30542cd4 0x30531000 + 72916
1 libsystem_c.dylib 0x379a030a 0x37996000 + 41738
2 libsystem_c.dylib 0x379a009c 0x37996000 + 41116
Thread 3:
0 libsystem_kernel.dylib 0x30542cd4 0x30531000 + 72916
1 libsystem_c.dylib 0x379a030a 0x37996000 + 41738
2 libsystem_c.dylib 0x379a009c 0x37996000 + 41116
Thread 4 name: WebThread
Thread 4:
0 libsystem_kernel.dylib 0x30532010 0x30531000 + 4112
1 libsystem_kernel.dylib 0x30532206 0x30531000 + 4614
2 CoreFoundation 0x37eb541c 0x37e28000 + 578588
3 CoreFoundation 0x37eb4154 0x37e28000 + 573780
4 CoreFoundation 0x37e374d6 0x37e28000 + 62678
5 CoreFoundation 0x37e3739e 0x37e28000 + 62366
6 WebCore 0x3290e128 0x32866000 + 688424
7 libsystem_c.dylib 0x379a5c16 0x37996000 + 64534
8 libsystem_c.dylib 0x379a5ad0 0x37996000 + 64208
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000000 r2: 0x00000001 r3: 0x00000000
r4: 0x00000006 r5: 0x3f7c2ce8 r6: 0x00000002 r7: 0x2fdffa6c
r8: 0x00000001 r9: 0x00000000 r10: 0x00000000 r11: 0x35cf9201
ip: 0x00000148 sp: 0x2fdffa60 lr: 0x379e3f5b pc: 0x3054232c
cpsr: 0x000f0010
You need to symbolicate the "Last Exception backtrace" to find out where in your app that crash happened.
To do that open terminal and go to the directory where the dSYM of that app version is located:
atos -arch armv7 -o your.app.dSYM/Contents/Resource/DWARF/binary 0x15b53 0x12ded 0x2c4b 0xb66d
Replace your.app.dSYM with the actual filename and binary with the filename inside the dSYM package in this directory) using the addresses in the apps address range (which you can find lower in the crash report below Binary Images). I added the ones which seem to be in it.
You can catch those crash reports yourself by using the open source PLCrashReporter framework and some other tools/services on top of it. Some even support automatic symbolication. I mentioned some options in this answer: https://stackoverflow.com/q/8242215/474794
For your kind of crash, it is important to know the last exception backtrace, or even other than the main thread. Only PLCrashReporter based solutions will provide you the information for that!
Since the error is SIGABRT, I would suggest checking all of your variables for leaks. I got this error all of the time when I was first working on my applications.
The best way to check:
Open Finder>Macintosh HD>Developer>Applications>Instruments
In XCode, rather than running the app, select Profile with Instruments open. Instruments will then pop up and ask you what to analyze. From the iOS Simulator submenu, select Memory>Zombies add and record. Run through your application to the point where your app crashed and Instruments should tell you what was accessed at that time.
Hope this helps
On a general practicality note, if you are looking for a better way to test your apps, (before release) I would strongly suggest TestFlight: https://testflightapp.com/
It permits 'on-the-fly' beta testing, and gives detailed crash reports such as this:
Device Name: iPhone
Model: iPhone 4
Version: 5.0
Language: en_US (English)
Carrier: Verizon
Timezone: EST
Architecture: armv7
Connection State: Cellular Active
Exception reason -[__NSCFArray objectAtIndex:]: index (0) beyond bounds (0)
Stacktrace (7) 0 Trail Tracker 0x0007ad89 +[TFCrashHandler backtrace] + 429
1 Trail Tracker 0x0007afc7 TFHandleExceptions + 35
2 CoreFoundation 0x34681987 __handleUncaughtException + 74
3 libobjc.A.dylib 0x3678c2d1 _objc_terminate + 128
4 libc++abi.dylib 0x372993c5 _ZL19safe_handler_callerPFvvE + 76
5 libc++abi.dylib 0x37299451 _ZdlPv + 0
6 libc++abi.dylib 0x3729a825 __cxa_current_exception_type + 0
7 libobjc.A.dylib 0x3678c235 objc_exception_rethrow + 12
8 CoreFoundation 0x345d7545 CFRunLoopRunSpecific + 404
9 CoreFoundation 0x345d73a5 CFRunLoopRunInMode + 104
10 GraphicsServices 0x34d4bfed GSEventRunModal + 156
11 UIKit 0x3613e743 UIApplicationMain + 1090
12 Trail Tracker 0x0001738b main (main.m:14)
13 Trail Tracker 0x00017344 start + 40
There is a lot that you can do with TestFlight, so check it out :)
PS: It's not my product, so sorry if it seems like I'm advertising/spamming. It's not my product, I just like it a lot. I thought that it pertained to this topic, due to the nature of the question. Cheers!