Bitcode app not symbolicating?

Hello,


I am struggling to understand why crash reports for my latest release are not fully symbolicated.


I just submitted an update for my app that enabled bitcode, and some users are experiencing a crash on launch that I can't seem to duplicate. But all the crash report in Xcode organizer gives me is this:


Last Exception Backtrace:
0   CoreFoundation                 0x183c642d8 __exceptionPreprocess + 132 (NSException.m:162)
1   libobjc.A.dylib               0x1954880e4 objc_exception_throw + 60 (objc-exception.mm:527)
2   CoreFoundation                 0x183c6b290 +[NSObject(NSObject) doesNotRecognizeSelector:] + 220 (NSObject.m:320)
3   CoreFoundation                 0x183c68154 ___forwarding___ + 928 (NSForwarding.m:2877)
4   CoreFoundation                 0x183b6accc _CF_forwarding_prep_0 + 92 (NSForwarding.s:770)
5   StopWatch                     0x10003ecf8 0x100008000 + 224504
6   StopWatch                     0x10003e9e8 0x100008000 + 223720
7   StopWatch                     0x10003be10 0x100008000 + 212496
8   StopWatch                     0x10003bae0 0x100008000 + 211680
9   UIKit                         0x1886bbf74 -[UIViewController _setViewAppearState:isAnimating:] + 516 (UIViewController.m:3456)
10  UIKit                         0x1887ddcec -[UITabBarController viewWillAppear:] + 244 (UITabBarController.m:562)
11  UIKit                         0x1886bbf74 -[UIViewController _setViewAppearState:isAnimating:] + 516 (UIViewController.m:3456)
12  UIKit                         0x1886ac83c -[UIView(Hierarchy) _willMoveToWindow:withAncestorView:] + 604 (UIView.m:6105)
13  UIKit                         0x1886abb74 -[UIView(Internal) _addSubview:positioned:relativeTo:] + 452 (UIView.m:9162)
14  UIKit                         0x1886ab360 -[UIWindow addRootViewControllerViewIfPossible] + 472 (UIWindow.m:1350)
15  UIKit                         0x1886a8880 -[UIWindow _setHidden:forced:] + 260 (UIWindow.m:1410)
16  UIKit                         0x18871a8ec -[UIWindow makeKeyAndVisible] + 56 (UIWindow.m:4507)
17  UIKit                         0x18892ea94 -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 2952 (UIApplication.m:1701)
18  UIKit                         0x188931208 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1504 (UIApplication.m:2662)
19  UIKit                         0x18892f778 -[UIApplication workspaceDidEndTransaction:] + 184 (UIApplication.m:2208)
20  FrontBoardServices             0x18c46d3c8 __31-[FBSSerialQueue performAsync:]_block_invoke_2 + 32 (FBSSerialQueue.m:112)
21  CoreFoundation                 0x183c1c27c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 20 (CFRunLoop.c:1638)
22  CoreFoundation                 0x183c1b384 __CFRunLoopDoBlocks + 312 (CFRunLoop.c:1675)
23  CoreFoundation                 0x183c199a8 __CFRunLoopRun + 1756 (CFRunLoop.c:2740)
24  CoreFoundation                 0x183b452d4 CFRunLoopRunSpecific + 396 (CFRunLoop.c:2795)
25  UIKit                         0x18871043c -[UIApplication _run] + 552 (UIApplication.m:2049)
26  UIKit                         0x18870afac UIApplicationMain + 1488 (UIApplication.m:3039)
27  StopWatch                     0x100041b0c 0x100008000 + 236300
28  libdyld.dylib                 0x195b06a08 start + 4 (start_glue.s:80)


Can anybody help me understand why this is happening? I made sure to download the dSYM's in Xcode organizer for this version of the app. And the UUID of the crash matches that of one of the dSYM's that Xcode downloaded.


Thanks,

James (MrRocketman)

Replies

I am having a similar problem like this.


Thread 0 Crashed:

0 MyApp 0x000000010010daa4 0x1000f4000 + 105124

1 MyApp 0x000000010010db04 0x1000f4000 + 105220

2 MyApp 0x000000010010cda0 0x1000f4000 + 101792

3 UIKit 0x0000000188a89324 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 400 (UIApplication.m:1789)

4 UIKit 0x0000000188cb7acc -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 2904 (UIApplication.m:2023)

5 UIKit 0x0000000188cbbe0c -[UIApplication _runWithMainScene:transitionContext:completion:] + 1656 (UIApplication.m:3253)

6 UIKit 0x0000000188cb8f50 -[UIApplication workspaceDidEndTransaction:] + 168 (UIApplication.m:2648)

7 FrontBoardServices 0x000000018d29f7c4 -[FBSSerialQueue _performNext] + 184 (FBSSerialQueue.m:157)

8 FrontBoardServices 0x000000018d29fb44 -[FBSSerialQueue _performNextFromRunLoopSource] + 56 (FBSSerialQueue.m:204)

9 CoreFoundation 0x0000000183438544 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 (CFRunLoop.c:1761)

10 CoreFoundation 0x0000000183437fd8 __CFRunLoopDoSources0 + 540 (CFRunLoop.c:1807)

11 CoreFoundation 0x0000000183435cd8 __CFRunLoopRun + 724 (CFRunLoop.c:2536)

12 CoreFoundation 0x0000000183364ca0 CFRunLoopRunSpecific + 384 (CFRunLoop.c:2814)

13 UIKit 0x0000000188a821c8 -[UIApplication _run] + 460 (UIApplication.m:2489)

14 UIKit 0x0000000188a7cffc UIApplicationMain + 204 (UIApplication.m:3665)

15 PGW 0x000000010010d2c8 0x1000f4000 + 103112

16 libdyld.dylib 0x00000001988828b8 start + 4 (start_glue.s:80)

The crash data I receive in Organizer also won't symbolicate.

anybody have any updates on this? we're having this same issue after adding in bitcode

Having the same issue.

I’m not an expert in this aspect of symbolication but my colleague, who is, recently update Technote 2151 Understanding and Analyzing iOS Application Crash Reports to cover it. Please take a look and let us know what you uncover.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I've been having this problem since May. The Crashes organizer was working great for me, then it wasn't working so great. https://forums.developer.apple.com/message/178764#178764


I wound up using the method described here to symbolicate, but it's a lot of steps - http://stackoverflow.com/questions/25855389/how-to-symbolicate-crash-log-xcode


The bug I filed, 27524602, did have some follow up from Apple but haven't heard anything more in a couple of months.

I have the exact same Problem with Xcode 8.2.1.


It would be awesome if an Apple Engineer could help us out. Where do we have to put the dSYMs files? We use a build server to submit the binaries to iTunesConnect and all developers get unsymbolicated crash reports in Xcode. We would like to use it as our main crashreporter tool, but it isn't usable as it is.


Please help us out or fix it in an upcoming release.

It would be awesome if an Apple Engineer could help us out.

Indeed it would. Alas, I seem to be the only Apple engineer who’s waded into this discussion and this is outside of my area of expertise. If you want formal help with this, I recommend you open a DTS tech support incident.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

We are about to enable Bitcode in our project, but unsolved issues regarding the symbolication of crashreports would be a show-stopper - are your problems resolved or still persistant?

I have just stumbled onto this thread as I also am suffering from un-symbolicated Device Logs.

Here's what I'mgetting:

Filtered syslog:
None found


Thread 0 name:  Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   libswiftCore.dylib             0x0084eff4 0x654000 + 2076660
1   libswiftCore.dylib             0x006abcdc 0x654000 + 359644
2   raceQs WatchKit Extension     0x001e9bbc 0x1c4000 + 154556
3   raceQs WatchKit Extension     0x001e525c 0x1c4000 + 135772
4   raceQs WatchKit Extension     0x001ddc94 0x1c4000 + 105620
5   raceQs WatchKit Extension     0x001ddf0c 0x1c4000 + 106252
6   CoreLocation                   0x21551da0 0x21537000 + 109984
7   CoreLocation                   0x2155169a 0x21537000 + 108186
8   CoreLocation                   0x2153d658 0x21537000 + 26200
9   CoreFoundation                 0x1cc95cf6 __CFRUNLOOP_IS_CALLING_


Running Xcode 9.3, iOS 11.4 and WatchOS 4.3

I have raised a bug report, but am not holding my breath!