Firebase Crashlytics does not display a crash report in the control panel on the Quick Launch

Question

I installed all of these steps and the package identifier on the Firesbase Dashboard and tried repeatedly to fail, but did not receive any report.

• pod 'Firebase / Core' pod 'Fabric', '~> 1.7.2' pod 'Crashlytics', '~> 3.9.3'
• When starting the build phase of the Script: "$ {PODS_ROOT} / Fabric / run
• Debug Inforation: DWARF format with dSYM file

• works in the simulator with the following steps

  • (IBAction) crashButtonTapped: (id) sender {[[Crashlytics sharedInstance] crash]; }

  • Click play_arrow Build, and then run the current circuit in Xcode to create an application on a device or simulator.

  • Click Stop. Stop executing a schema or action in Xcode to close the source instance of your application. This source instance includes a debugger that interferes with Crashlytics.
  • Open the application again from the simulator or device. Click "Fail" to disable the application.

Answer 1

I took the same steps as you, and thought that I had a problem until I realized that there was a delay in the appearance of accidents on the console. In my case, it took about 40 minutes.

Here is a blog post about it.

Answer 2

Check startup script only during installation

Answer 3

In my case,

After the crash, I opened the application. The crash report is updated in the Firebase console within a minute.

Answer 4

I did everything that happened on the stack, my download was successful, but nothing appeared. Trying to find a solution, I tried it, and it worked for me as well as for other people facing the same problem, can help others who find themselves here.

I posted it in the questions section to check it https://github.com/firebase/quickstart-ios/issues/413

One thing I did was move my test crash

Crashlytics.sharedInstance().crash() 

to the first view controller, such as WelcomeViewController, and then after a crash, I closed and reopened my application. Then he just waited once, and he appeared.

Before doing all this, my test crash was in the view controller, which was part of the tabBarController, because maybe it was not the most important view controller, which caused the problem. After the first crash that appeared on the firebase console, my other crashes appeared.

Answer 5

If you have to rebuild an application that has already used Crashlytics and is migrating to Firebase, be sure to make sure your API key is still included in your .plist and run the script, and that Crashlytics is initialized through the documentation here:

https://fabric.io/kits/ios/crashlytics/install

Your application will be created, and Firebase will be able to determine the overall frequency of failures, but will not receive any of the individual reports.

Answer 6

Check your app id in app, for example. The package identifier is abc_app , go to the console project of the Firebase application through OverView → the project settings, and then select your application in the "Your application" section and make sure that the package identifier in the application and the package identifier in the Firebase application. Both must be the same!