I have an iPad app out in the field (enterprise distribution) that randomly stopped working (after about 150 uses). It loads the black screen like its about to open but then flashes back to the main screen.
The app remains in the running list, but will not open. After resetting the iPad and reinstalling the app, it runs fine again. The crash report is as follows:
Incident Identifier: 97E6C3AC-0A3F-4D5A-9316-14361B8875C8
CrashReporter Key: acbe2088ab1236c4f317ec9e0fb85d4a9d7b5b3a
Hardware Model: iPad1,1
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2011-08-05 14:52:54.380 -0400
OS Version: iPhone OS 4.3.2 (8H7)
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread: 0
Thread 0 Crashed:
0 dyld 0x2fe0124a dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*) + 446
1 dyld 0x2fe01058 _dyld_start + 48
Thread 0 crashed with ARM Thread State:
r0: 0x00000000 r1: 0x00000009 r2: 0x00000009 r3: 0x0004a000
r4: 0x0004a01c r5: 0x00000000 r6: 0x00000005 r7: 0x2fe48a18
r8: 0x2fe6f18c r9: 0x2fe96964 r10: 0x2fe494f4 r11: 0x00049000
ip: 0x2fe96984 sp: 0x2fe489d0 lr: 0x2fe489ac pc: 0x2fe4a24a
cpsr: 0x60000030
Binary Images:
0x2fe49000 - 0x2fe6efff dyld armv7 <bb9bfc7d242331d29a79adf7ef7aaa18> /usr/lib/dyld
This is all the information the report contains.
We've never been able to reproduce the crash on the simulator.
Any ideas? Can't send this back out until we make sure the error is fixed. Thanks,
Freezing and crashing apps are usually due to memory-related issues like when the device is running low on internal storage. The same thing can happen if the application gets corrupted after installing updates and likewise when an app isn't up-to-date.
Apps on Android can crash because of low storage space, too many apps running simultaneously, a weak internet connection, or not having the proper app updates installed.
Your iPad probably keeps crashing because of pending software updates, battery-related issues, third-party applications that are incompatible, or malware or virus intrusions.
Most often, apps crash because they aren't updated and have unaddressed bugs. To fix this, go to the Updates section of the App Store and update the app if an update is available.
The system is probably killing the app because the provisioning profile has expired. If you can get access to the old app (e.g. by syncing with iTunes and then doing Reveal in Finder
on the app) then you can find the provisioning profile inside the app as embedded.mobileprovision
which you can inspect to determine if it has expired.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With