React-native-firebase: [🐛] Unable to register a new iOS app with Firebase Crashlytics

[anhtuank7c]

Issue

I unable to register a new iOS app with Firebase Crashlytics.
Firebase dashboard keeps loading.
I could do it on Android but iOS seems to load forever (at least half-day without changes)
Note: Firebase Analytics and Performance still work very well and I can track it on Firebase dashboard

Project Files

Javascript

import crashlytics from '@react-native-firebase/crashlytics'

<Button label="Force a Crash" onPress={() => crashlytics().crash()} />

package.json:

"dependencies": {
    "@react-native-firebase/analytics": "^10.0.0",
    "@react-native-firebase/app": "^10.0.0",
    "@react-native-firebase/crashlytics": "^10.0.0",
    "react": "16.13.1",
    "react-native": "0.63.3",
  },

firebase.json for react-native-firebase v6:

{
  "react-native": {
    "crashlytics_auto_collection_enabled": true,
    "crashlytics_debug_enabled": true,
    "crashlytics_disable_auto_disabler": true
  }
}

iOS

ios/Podfile:

• [ ] I'm not using Pods
• [x] I'm using Pods and my Podfile looks like:

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '11.4'

target 'example' do
  inhibit_all_warnings! # hide all warnings

  config = use_native_modules!
  use_react_native!(:path => config["reactNativePath"])

  target 'exampleTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable these next few lines.
  use_flipper!
  post_install do |installer|
    flipper_post_install(installer)
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.4' #Force all dependencies to use deployment target 11.4 since React Native Navigation required 11.0 and up
      end
    end
  end
end

target 'example-tvOS' do
  # Pods for example-tvOS

  target 'example-tvOSTests' do
    inherit! :complete
    # Pods for testing
  end
end

AppDelegate.m:

// N/A

Environment

Click To Expand

**`react-native info` output:**

System:
    OS: macOS 11.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 428.36 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.10.1 - ~/.nvm/versions/node/v14.10.1/bin/node
    Yarn: 1.22.5 - ~/.nvm/versions/node/v14.10.1/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.10.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
    Android SDK:
      Android NDK: 22.0.6917172-beta1
  IDEs:
    Android Studio: 4.1 AI-201.8743.12.41.6953283
    Xcode: 12.2/12B45b - /usr/bin/xcodebuild
  Languages:
    Java: 13.0.2 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.3 => 0.63.3 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

- **Platform that you're experiencing the issue on**: - [x] iOS - [ ] Android - [ ] **iOS** but have not tested behavior on Android - [ ] **Android** but have not tested behavior on iOS - [ ] Both - **`!@react-native-firebase/crashlytics` version you're using that has this issue:** - `^10.0.0` - **`Firebase` module(s) you're using that has the issue:** - `Crashlytics` - **Are you using `TypeScript`?** - `Y`

[ahtisham09]

I am getting same issue from last three weeks

[mikehardy]

Have you triggered a test crash then restarted the app (so the crash sends)? You didn't specify

I know that Crashlytics was somewhat hooked to analytics for detection if you had connected or not to get past that page, but with a test crash uploaded it should work

[anhtuank7c]

@mikehardy I did trigger some test cash, restart the app, simulator in both js and native side.
For Js: crashlytics().crash()
For native Swift: fatalError()
Besides that, the Firebase Analytics work just fine and I could see the analytics summary in the Firebase Dashboard.

[mikehardy]

That is really frustrating! I'm not sure what it could be then. You're sure dsyms are uploaded?

[anhtuank7c]

@mikehardy Yes of course. I uploaded it manually.

[anhtuank7c]

I added some more information to this issue:

Crashlytics log in xCode

Upload dSYM file result

Analytics Dashboard

[mikehardy]

what is weird is that it does not show any unsent reports. It thinks it is sending them - when there are unsent reports you can see them in the logs normally (and I think we recently added an API to get the count?). I sincerely apologize, but I'm stumped on this one

[anhtuank7c]

Alright, I push code to this repo. Please help to check it out.
https://github.com/anhtuank7c/rnfbdemo

[jnrepo]

@anhtuank7c I had a similar experience to you. I had to go ahead and add $FirebaseSDKVersion = '7.0.0' to this line here in the Podfile and it seems to work now. Hope it helps.

Based off docs

[mikehardy]

As a note, if you do that, you are now responsible for tracking the underlying SDK releases yourself, you won't automatically get updates pulled in by our default setting in @react-native-firebase/app. We are already on 7.1.0 in app, and 7.2.0 is out and tested and working and I'll release it as v10.2.0 here shortly but your override will keep you on 7.2.0 unless you track https://firebase.google.com/support/release-notes/ios yourself and do the updates. As with all things this is not good or bad, just tradeoffs.

Cheers!

[sagarguhe]

I am as well facing the same issue.. Android works fine.

[Copdate-Copdate]

Got the same issue. When testing and looking at xCode console, I got the following when calling await crashlytics().crash();:

Maybe it can help

[mikehardy]

Images never really help me when debugging sorry. Full stack traces pasted in triple-backticks (for github markdown formatting) help

[mikehardy]

@Copdate-Copdate it is documented that if you try to do a test crash while a debugger is attached it will capture the crash. So it's working as expected.