Multiple <compiler-generated> crashes showing in Firebase Crashlytics with wrong line number

I have multiple crashes showing in Firebase Crashlytics.

This crashes are not present in Xcode organizer!!!

All these crashes are from TestFlight.

First crash

Crashed: com.apple.main-thread
0  UltimaPayments                 0x60f8c viewWillAppear + 4368338828 (TransactionsListViewController.swift:4368338828)
1  UltimaPayments                 0x60fcc viewWillAppear + 4368338892 (<compiler-generated>:4368338892)
2  UIKitCore                      0x1ab288 -[UIViewController _setViewAppearState:isAnimating:] + 664
3  UIKitCore                      0x2d952c -[UIViewController __viewWillAppear:] + 120
4  UIKitCore                      0x3a9314 -[UITabBarController transitionFromViewController:toViewController:transition:shouldSetSelected:] + 1260
5  UIKitCore                      0x2ebf10 -[UITabBarController _setSelectedViewController:] + 428
6  UIKitCore                      0x25bcb0 -[UITabBarController setSelectedViewController:] + 116
7  UltimaPayments                 0x7f278 selectedViewController.set + 4368462456 (<compiler-generated>:4368462456)
8  UIKitCore                      0x8feb08 -[UITabBarController _setSelectedViewControllerAndNotify:] + 604

Second

Crashed: com.apple.main-thread
0  UltimaPayments                 0x2e59c viewDidLoad + 4297270684 (SessionPayViewController.swift:4297270684)
1  UltimaPayments                 0x2e618 viewDidLoad + 4297270808 (<compiler-generated>:4297270808)
2  UIKitCore                      0x1abffc -[UIViewController _sendViewDidLoadWithAppearanceProxyObjectTaggingEnabled] + 108
3  UIKitCore                      0x1aeb4c -[UIViewController loadViewIfRequired] + 1048
4  UIKitCore                      0x181bac -[UIViewController view] + 32
5  UIKitCore                      0x377494 -[UINavigationController _startCustomTransition:] + 1140
6  UIKitCore                      0x4d569c -[UINavigationController _startDeferredTransitionIfNeeded:] + 696
7  UIKitCore                      0x3aae1c -[UINavigationController __viewWillLayoutSubviews] + 168
8  UIKitCore                      0x2d25dc -[UILayoutContainerView layoutSubviews] + 228
9  UIKitCore                      0x18c17c -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2592
10 QuartzCore                     0x407fc CA::Layer::layout_if_needed(CA::Transaction*) + 532
11 QuartzCore                     0x32c60 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 136
12 QuartzCore                     0x475b4 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 452
13 QuartzCore                     0x504a8 CA::Transaction::commit() + 704
14 QuartzCore                     0x323a0 CA::Transaction::flush_as_runloop_observer(bool) + 88
15 CoreFoundation                 0x410c4 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
16 CoreFoundation                 0x10080 __CFRunLoopDoObservers + 592
17 CoreFoundation                 0xb13c __CFRunLoopRun + 1052
18 CoreFoundation                 0x1ebc8 CFRunLoopRunSpecific + 600
19 GraphicsServices               0x1374 GSEventRunModal + 164
20 UIKitCore                      0x514b58 -[UIApplication _run] + 1100
21 UIKitCore                      0x296090 UIApplicationMain + 364
22 UltimaPayments                 0x58a0 main + 18 (AccessRights.swift:18)
23 ???                            0x1009ddda4 (Missing)

Why there is wrong line number showing where crash occured? Why this kind of crashes are not present in organizer?

Answered by DTS Engineer in 726275022

Why this kind of crashes are not present in organizer?

It’s hard to offer concrete advice here. You’re relying on a third-party crash reporter and it’s impossible to create one that works reliable. For background on this, see my Implementing Your Own Crash Reporter post. It’s possible that these crash reports aren’t ‘real’. It’s also possible that your third-party crash reporter is disrupting the Apple crash reporter (see the Preserve the Apple Crash Report section of that post). It’s also possible that the Apple crash reporter is messing up.

The only way to untangle this mess IMO is to disable the third-party crash reporter and see what crashes you’re left with.

Why there is wrong line number showing where crash occured?

That’s something you need to ask the vendor.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Accepted Answer

Why this kind of crashes are not present in organizer?

It’s hard to offer concrete advice here. You’re relying on a third-party crash reporter and it’s impossible to create one that works reliable. For background on this, see my Implementing Your Own Crash Reporter post. It’s possible that these crash reports aren’t ‘real’. It’s also possible that your third-party crash reporter is disrupting the Apple crash reporter (see the Preserve the Apple Crash Report section of that post). It’s also possible that the Apple crash reporter is messing up.

The only way to untangle this mess IMO is to disable the third-party crash reporter and see what crashes you’re left with.

Why there is wrong line number showing where crash occured?

That’s something you need to ask the vendor.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Multiple &lt;compiler-generated&gt; crashes showing in Firebase Crashlytics with wrong line number
 
 
Q