React-native-firebase: Question : Upgrade to the Firebase Crashlytics SDK from Fabric

Created on 10 Jun 2020  ·  8Comments  ·  Source: invertase/react-native-firebase


Issue



We just received a mail from Firebase :
[Action Required] Update your apps to use the latest Firebase Crashlytics SDKs before November 15, 2020.

FirebaseCrashlytics no longer works with the Fabric SDK

Is there any plan for this?

Thanks


Project Files






Javascript

Click To Expand

#### `package.json`:

# N/A
#### `firebase.json` for react-native-firebase v6:
# N/A
### iOS
Click To Expand

#### `ios/Podfile`: - [ ] I'm not using Pods - [x] I'm using Pods and my Podfile looks like:

# N/A
#### `AppDelegate.m`:
// N/A


Android

Click To Expand

#### Have you converted to AndroidX? - [ ] my application is an AndroidX application? - [ ] I am using `android/gradle.settings` `jetifier=true` for Android compatibility? - [ ] I am using the NPM package `jetifier` for react-native compatibility? #### `android/build.gradle`:

// N/A
#### `android/app/build.gradle`:
// N/A
#### `android/settings.gradle`:
// N/A
#### `MainApplication.java`:
// N/A
#### `AndroidManifest.xml`:
<!-- N/A -->


Environment

Click To Expand

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

 OUTPUT GOES HERE
- **Platform that you're experiencing the issue on**: - [ ] iOS - [ ] Android - [ ] **iOS** but have not tested behavior on Android - [ ] **Android** but have not tested behavior on iOS - [ ] Both - **`react-native-firebase` version you're using that has this issue:** - `e.g. 5.4.3` - **`Firebase` module(s) you're using that has the issue:** - `e.g. Instance ID` - **Are you using `TypeScript`?** - `Y/N` & `VERSION`




Most helpful comment

(for anyone else that lands here, we've got till November, and there's a PR that already exists, should merge soon enough)

All 8 comments

Failing to search is failing to respect volunteer maintainer time

https://github.com/invertase/react-native-firebase/issues?q=fabric+deprecated

(for anyone else that lands here, we've got till November, and there's a PR that already exists, should merge soon enough)

Hey @mikehardy – it the PR you refer to already merged?
I’m facing the same issue after upgrading from Fabric: crash appears on Android dashboard, but not on iOS

Hey @mikehardy – it the PR you refer to already merged?
I’m facing the same issue after upgrading from Fabric: crash appears on Android dashboard, but not on iOS

Yes. You're having a related but new issue. Has a fix that needs someone to test and confirm and PR, it's tiny and easy, could be you 😁, check issues list sorted by recently updated, was just updated couple of hours ago

Yay! It worked! Thank you so much for the fast reply!
image

This fix relates only to the usage of the testing crash method, right?

Is there an option to see the JS stack trace? as I don’t see it (I triggered the crash by pressing a button)

Uploading image.png…

yes - this is just for test crash only, actual crashes are working but obviously if the test method doesn't give expected results it casts doubt on the whole thing which is unfortunate

there is no JS stack trace in the test crash method, it's a native crash, but you will see non-symbolicated JS stack traces if you take a JS crash, yes. Care to PR the switch to native-test-crash code? All the internet points could be yours :smile: :nerd_face:

Sure, will do tomorrow! 😊

Was this page helpful?
0 / 5 - 0 ratings

Related issues

joecaraccio picture joecaraccio  ·  3Comments

dgruseck picture dgruseck  ·  3Comments

escobar5 picture escobar5  ·  3Comments

n-scope picture n-scope  ·  3Comments

callmejm picture callmejm  ·  3Comments