I'm having problems with an app that we previously submitted to Apple for submission that they asked us to re-do a simple marketing issue (we needed to remove an image of an app screen which had third party apps).
Unfortunately, now when I have prepared the app for re-submission and I distribute it via Testflight the app crashes on launch. A subsequent launch works, however. This only happens with the Testflight build - when I do a Release build from Xcode using a production provisioning profile it works, and when I do a debug build it works. Thinking I must have made a mistake I pulled the exact commit from my repo for the previous submission, but it is now crashing the exact same way.
Only my ipad mini 2 reports the crash logs via the Xcode Organizer (my iPhone 6 does not), and they read like this (though I checked the box to include the debug symbols):
Incident Identifier: BDC2E493-9794-42D8-B9F6-F74DEF432AA2
Beta Identifier: F34F1B0B-44F0-4E9C-A8F6-46861EDB0B39
Hardware Model: iPad4,4
Process: My App [6660]
Path: /private/var/mobile/Containers/Bundle/Application/1EDC2E96-E4E0-4148-AF7D-478A8C2FA5D9/My App.app/My App
Identifier: com.myco.My-App
Version: 29 (1.0)
Beta: YES
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2015-10-02 11:49:41.41 -0700
Launch Time: 2015-10-02 11:49:39.39 -0700
OS Version: iOS 9.0 (13A341)
Report Version: 105
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000001004b4f5c
Triggered by Thread: 0
Thread 0 name:
Thread 0 Crashed:
0 libswiftCore.dylib 0x00000001004b4f5c specialized _fatalErrorMessage(StaticString, StaticString, StaticString, UInt) -> () + 44
1 My App 0x000000010011bb50 0x1000fc000 + 129872
2 My App 0x000000010010e954 0x1000fc000 + 76116
3 libdispatch.dylib 0x0000000198b817b0 _dispatch_call_block_and_release + 24 (init.c:761)
4 libdispatch.dylib 0x0000000198b81770 _dispatch_client_callout + 16 (object.m:513)
5 libdispatch.dylib 0x0000000198b86e20 _dispatch_main_queue_callback_4CF + 1844 (inline_internal.h:1063)
6 CoreFoundation 0x0000000183a78258 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 (CFRunLoop.c:1615)
7 CoreFoundation 0x0000000183a760c0 __CFRunLoopRun + 1628 (CFRunLoop.c:2721)
8 CoreFoundation 0x00000001839a4dc0 CFRunLoopRunSpecific + 384 (CFRunLoop.c:2814)
9 GraphicsServices 0x000000018e920088 GSEventRunModal + 180 (GSEvent.c:2247)
10 UIKit 0x000000018907ef60 UIApplicationMain + 204 (UIApplication.m:3663)
11 My App 0x000000010011afe8 0x1000fc000 + 126952
12 libdyld.dylib 0x0000000198bb28b8 start + 4 (start_glue.s:80)
I can't figure out what's causing this, nor how I'll be able to test and confirm it's fix without re-submitting to Testflight and waiting.
I suspect this may be an Apple problem, but I'm nervous about re-submitting knowing there may be a crash in my app. Does anyone know what might cause this?
Related
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
I usually develop in higher level languages like Javascript and Python , so I am not that experienced when it comes to reading lower level stack traces. I am building an iOS app with React Native and my app sometimes unexpectedly crashes. Reading the crash log this is what I get:
Incident Identifier: B03D5F95-EFD1-4FEB-AE18-C8EFEF273E53
CrashReporter Key: 6049c1cc93a2e0163265631aa6cc2fd30a1af6e7
Hardware Model: iPhone7,2
Process: MyApp [24268]
Path: /private/var/containers/Bundle/Application/99B2B9A1-D266-4222-A083-84C4CFFCE182/MyApp.app/MyApp
Identifier: org.mycompany.MyApp
Version: 1 (1.0)
Code Type: ARM-64 (Native)
Role: Non UI
Parent Process: launchd [1]
Coalition: org.mycompany.MyApp [3119]
Date/Time: 2019-03-04 14:20:18.4924 +0800
Launch Time: 2019-03-04 14:09:15.2536 +0800
OS Version: iPhone OS 11.0.3 (15A432)
Baseband Version: 6.17.00
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace <0xF>, Code 0x8badf00d
Triggered by Thread: 0
Filtered syslog:
None found
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000180a60bc4 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x0000000180a60a3c mach_msg + 72
2 BackBoardServices 0x00000001835d0de0 _BKSHIDGetCurrentDisplayBrightness + 112
3 BackBoardServices 0x00000001835de9cc BKSDisplayBrightnessGetCurrent + 32
4 FrontBoardServices 0x00000001835fffc0 -[FBSUIApplicationSystemService currentBacklightLevel] + 12
5 UIKit 0x000000018a8a3d44 -[UIDevice _backlightLevel] + 44
6 UIKit 0x000000018a8aced4 -[UIScreen _postBrightnessDidChangeNotificationIfAppropriate] + 168
7 CoreFoundation 0x0000000180efa12c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 20
8 CoreFoundation 0x0000000180efa090 ___CFXRegistrationPost_block_invoke + 64
9 CoreFoundation 0x0000000180f1016c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 20
10 CoreFoundation 0x0000000180f0fa3c __CFRunLoopDoBlocks + 288
11 CoreFoundation 0x0000000180f0dca4 __CFRunLoopRun + 2436
12 CoreFoundation 0x0000000180e2e2d8 CFRunLoopRunSpecific + 436
13 GraphicsServices 0x0000000182cbff84 GSEventRunModal + 100
14 UIKit 0x000000018a3db880 UIApplicationMain + 208
15 MyApp 0x00000001005833d4 main + 29652 (main.m:14)
16 libdyld.dylib 0x000000018095256c start + 4
How/where do I begin reading thsi crash log? I believe it has something to do with mach_msg_trap but I haven't been able to find anything about it. For some context, my app is an app which tracks the users Geolocation with background geolocation tracking. I am unable to figure out what causes the crash.
See TN2141: Understanding and Analyzing Application Crash Reports, which says:
The exception code 0x8badf00d indicates that an application has been terminated by iOS because a watchdog timeout occurred. The application took too long to launch, terminate, or respond to system events. ... Whatever operation is on Thread 0 needs to be moved to a background thread, or processed differently, so that it does not block the main thread.
Are you doing anything that could be blocking the main thread for any prolonged period of time?
Have you add Privacy - Location in info.plist?
Something like that.
<key>NSLocationAlwaysUsageDescription</key>
<string>Why you need track location?</string>
<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>Why you need track location?</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>Why you need track location?</string>
And I see you work with background geolocation tracking. Have you turn on Background Modes in Capabilities?
If not just add Privacy turn on Background Modes and try again.
I am unable to find the reason of the crash. I know that the user was signing on to Game Centre. However, this was followed by the user starting to play 'MyApp'. I still can't find the error. I have read Apple tech doc and the 2010 video. Still unable to find the problem. Please help.
Incident Identifier: D3A80086-855D-400D-8102-7D08D04C2A4D
CrashReporter Key: 6b4377c06adbfe5d64bfb9dd348bd73e93859214
Hardware Model: iPhone5,4
Process: MyApp [280]
Path: /private/var/mobile/Containers/Bundle/Application/D5470DBE-1FF8-4E06-946B-910AD698DD2D/MyApp.app/MyApp
Identifier: MyApp
Version: 4 (4.86)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2015-12-26 01:10:15.15 +0400
Launch Time: 2015-12-26 01:06:30.30 +0400
OS Version: iOS 9.2 (13C75)
Report Version: 105
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x00000000e7ffdefe
Triggered by Thread: 0
Filtered syslog:
None found
Breadcrumb Trail: (reverse chronological seconds)
6 logging-started
6 GC TBG: lookForEvent
224 GC Framework: startAuthenticationForExistingPrimaryPlayer
Global Trace Buffer (reverse chronological seconds):
6.978571 GameCenterFoundation 0x000000002eb776e1 callAuthHandlerWithError:Setting the Authentication Handler
6.989052 GameCenterFoundation 0x000000002eb886f5 GKMatchMaker: lookForInvite
6.989130 GameCenterFoundation 0x000000002ebb05d9 updateNearbyAdvertising
6.989130 GameCenterFoundation 0x000000002eb88485 finishedAuthenticating: Starting nearby Advertising and looking for invites
6.989724 GameCenterFoundation 0x000000002eb87f49 GKMatchmaker: loadConnectivitySettingsWithCompletionHandler
6.990383 GameCenterFoundation 0x000000002eb77663 Calling AuthenticationHandlerWithError: 0
7.056258 GameCenterUI 0x000000002f8067fd authenticationDidCompleteWithError:Local Player Authenticated, showing Welcome Banner
7.056258 GameCenterUI 0x000000002f8065f7 authenticationDidCompleteWithError being called
214.506726 GameCenterUI 0x000000002f8074e3 authenticationShowSignInUIForLocalPlayer:Showing sign in view controller
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 MyApp 0x000e8160 0xce000 + 106848
1 GameCenterFoundation 0x2ebc92c4 __39-[GKDispatchGroup notifyOnQueue:block:]_block_invoke53 + 12
2 libdispatch.dylib 0x228abdd6 _dispatch_call_block_and_release + 10
3 libdispatch.dylib 0x228abdc2 _dispatch_client_callout + 22
4 libdispatch.dylib 0x228b0670 _dispatch_main_queue_callback_4CF + 1532
5 CoreFoundation 0x22cd0fc4 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 8
6 CoreFoundation 0x22ccf4be __CFRunLoopRun + 1590
7 CoreFoundation 0x22c21bb8 CFRunLoopRunSpecific + 516
8 CoreFoundation 0x22c219ac CFRunLoopRunInMode + 108
9 GraphicsServices 0x23e9baf8 GSEventRunModal + 160
10 UIKit 0x26f0dfb4 UIApplicationMain + 144
11 MyApp 0x000daa08 0xce000 + 51720
12 libdyld.dylib 0x228d4872 start + 2
I have this exactly same problem.
The apple reviewer report to check if my app is IPv6 compatible.
I reply him that my app use only Game Center to communicate, if this is a IPv6 problem, this should be a Game Center problem.
Anyway, in my experience, testing my app, this only happened when I change from Main Menu to Game Mode menu when the "Game Center Authentication Banner" is opened.
My game is developed in SceneKit and the menus are developed using SpriteKit inside the SceneView on Overlay layer.
To switch menus, I just change the SKScene in SceneView.
I have developed an iPad application using Xcode 6.3.2.
I submitted my application to the App Store for review where it was reject due to crash.Following is the crash report from iTunes.
Incident Identifier: 88DD7F94-3382-4241-A0D7-C3E7F6D20737
CrashReporter Key: 9881ae0cc3b3fbfccfd0ce1496d2fa08fec08782
Hardware Model: xxx
Path: /private/var/mobile/Containers/Bundle/Application/FDBBD67F-0EF7-43FB-80CB-8308A10A2D29/Vehicle Visuals.app/Vehicle Visuals
Identifier: com.vehiclevisuals.Vehicle-Visuals
Version: 2.0.0 (1.1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2015-06-12 12:33:57.988 -0700
Launch Time: 2015-06-12 12:22:14.581 -0700
OS Version: iOS 8.3 (12F69)
Report Version: 105
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x0000000195da7bdc 0x195d8c000 + 113628
1 QuartzCore 0x00000001889fdc2c 0x1889ec000 + 72748
2 Vehicle Visuals 0x0000000100126828 0x1000ec000 + 239656
3 Vehicle Visuals 0x0000000100101e80 0x1000ec000 + 89728
4 UIKit 0x0000000189118778 0x1890a4000 + 477048
5 UIKit 0x0000000189116750 0x1890a4000 + 468816
6 UIKit 0x0000000189112000 0x1890a4000 + 450560
7 UIKit 0x00000001890b175c 0x1890a4000 + 55132
8 QuartzCore 0x00000001889f9e18 0x1889ec000 + 56856
9 QuartzCore 0x00000001889f4880 0x1889ec000 + 34944
10 QuartzCore 0x00000001889f4724 0x1889ec000 + 34596
11 QuartzCore 0x00000001889f3eb8 0x1889ec000 + 32440
12 QuartzCore 0x00000001889f3c38 0x1889ec000 + 31800
13 UIKit 0x0000000189137f8c 0x1890a4000 + 606092
14 UIKit 0x0000000189137ef0 0x1890a4000 + 605936
15 CoreFoundation 0x000000018462c2a0 0x18454c000 + 918176
16 CoreFoundation 0x000000018462922c 0x18454c000 + 905772
17 CoreFoundation 0x000000018462955c 0x18454c000 + 906588
18 CoreFoundation 0x00000001845552d0 0x18454c000 + 37584
19 GraphicsServices 0x000000018dc436f8 0x18dc38000 + 46840
20 UIKit 0x000000018911afa8 0x1890a4000 + 487336
21 Vehicle Visuals 0x000000010013a1cc 0x1000ec000 + 319948
22 libdyld.dylib 0x0000000196412a04 0x196410000 + 10756
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
As per the report it crashes on OS Version : iOS 8.3 (12F69).
I tested my app on the all simulators(iPad Air, iPad 2, iPad Retina) with same config(iOS version 8.3 (12F69)) and also tested it on my device (iPad mini) with iOS version 8.3 (12F69), but didn't crashed on my side.
But it crashes on my friend's iPad Air with same iOS version (it gives the same crash report with different invalid address as below)
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype:
KERN_INVALID_ADDRESS at 0x0000000000000020 Triggered by Thread: 0
I don't have the iPad Air so that I could debug using the device.
I also tried to Symbolicated crash report using following command.
xcrun atos -o VehicleVisuals 0x0000000000000020
But it just gives me following hex code.
0x00000020 (in VehicleVisuals)
I following Link for symbolication.
I'm just not being able to recognise where actually is the crash issue.
Please can anybody help me out?
EXC_BAD_ACCESS usually happens because you are sending an Obj-C message to an invalid memory address, what means that you probably are trying to access some deallocated object.
It may be working on other devices because this object is not being released at the same time.
I recently had a similar crash that happened because there was a timer not being invalidated on dealloc, and when the target method was called, that object did no longer exist.
You could try to enable NSZombie objects and see if you find which object is being deallocated. In xCode 6, you can enable them in Product > Scheme > Edit scheme > Diagnostics > Enable Zombie Objects.
Also, there are lots of these kind of errors that NSZombieEnabled can't detect. Unfortunately there is nothing magical to solve it. The second option would be to run your app with instruments (memory leaks specifically) and see if you can get something. If this doesn't work you will have to review your code and check that there are no possibilities that you are trying to access a deallocated object. Hope it helps.
Good luck!
I am building a mobile app using PhoneGap and I have send it to Beta using TestFlight. Everyone has been able to download and test the app except for one user out of roughly 10. He can install the app perfectly fine, but when he goes to launch it, it crashes immediately. The first time he tried he got into the app, but when gave permissions to a plugin it crashed.
He provided me with a crash log, which I've shortened to:
Incident Identifier: BE251DD5-6D68-4084-84F6-EC629B24F2CA
CrashReporter Key: 7cccfe6ca4af8513c8cdb2fc1cacf253a416553b
Hardware Model: iPhone6,1
Process: Loaner [1549]
Path: /var/mobile/Applications/5B7BB625-9A3D-4ACE-A8A0-74424577067C/Loaner.app/Loaner
Identifier: com.cardeninteractive.loaner
Version: 1.1d (1.1d)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2014-05-27 11:54:57.681 -0400
OS Version: iOS 7.1.1 (11D201)
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x0000000185806198 Triggered by Thread: 0 Thread 0 Crashed:
0 CoreFoundation 0x0000000185806198 0x185800000 + 24984
1 Loaner 0x00000001000407b4 0x100020000 + 133044
2 Loaner 0x000000010003ec64 0x100020000 + 126052
3 Loaner 0x0000000100039174 0x100020000 + 102772
4 Loaner 0x000000010003a25c 0x100020000 + 107100
5 libdispatch.dylib 0x00000001923ebfd0 0x1923e8000 + 16336
6 libdispatch.dylib 0x00000001923f3834 0x1923e8000 + 47156
7 libdispatch.dylib 0x00000001923ebfd0 0x1923e8000 + 16336
8 libdispatch.dylib 0x00000001923ef1d8 0x1923e8000 + 29144
9 CoreFoundation 0x00000001858cac28 0x185800000 + 830504
10 CoreFoundation 0x00000001858c8f68 0x185800000 + 823144
11 CoreFoundation 0x0000000185809c1c 0x185800000 + 39964
12 GraphicsServices 0x000000018b4f1c08 0x18b4e4000 + 56328
13 UIKit 0x000000018893afd8 0x1888c0000 + 503768
14 Loaner 0x0000000100035f68 0x100020000 + 89960
15 libdyld.dylib 0x0000000192407a9c 0x192404000 + 15004
I have read a number of posts on SO and can't seem to gain any insight into this.
Both myself and this guy are using an iPhone 5S and the problem doesn't affect me at all, even if I download the build from TestFlight and not through the IDE.