🔥 [🐛] setCrashlyticsCollectionEnabled crashes some Huawei Device on startup

[vlack-coder]

Issue

Describe your issue here
There are a lot of crash issues on Huawei phones. I've attached screenshots from the firebase console and the crash is pointing to the oncreate function of the crashlytics

  @Override
  public boolean onCreate() {
    super.onCreate();

    try {
      FirebaseCrashlytics.getInstance()
          .setCrashlyticsCollectionEnabled(
              ReactNativeFirebaseCrashlyticsInitProvider.isCrashlyticsCollectionEnabled());
      Log.i(TAG, "initialization successful");
    } catch (Exception exception) {
      Log.e(TAG, "initialization failed", exception);
      return false;
    }

    return true;
  }
}

---

Crash

Bug Description

Devices Affected

Android OS Version Affected

Javascript

Click To Expand

package.json:

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?

---

Project Files

        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.9.2'
        classpath 'com.google.firebase:perf-plugin:1.4.2'

        firebaseCrashlytics {
            nativeSymbolUploadEnabled true
            unstrippedNativeLibsDir 'build/intermediates/merged_native_libs/release/out/lib'
        }

---

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:
  • "18.9.0",
• Firebase module(s) you're using that has the issue:
  • @react-native-firebase/crashlytics":
• Are you using TypeScript?
  • Y & 4.8.4

---

• 👉 Check out React Native Firebase and Invertase on Twitter for updates on the library.

[vlack-coder]

The Crash is most likely from the native side and it happens before the react native engine is initialized.
The main culprit here is the

FirebaseCrashlytics.getInstance()
  .setCrashlyticsCollectionEnabled(...)

in the

ReactNativeFirebaseCrashlyticsInitProvider.onCreate()

My Dexguard Rules

-keep class com.google.firebase.crashlytics.** { *; }
-keep class com.google.firebase.** { *; }
-keep class com.google.firebase.messaging.** { *; }
-raspdenylist class com.google.firebase.crashlytics.** { *; }
-raspdenylist class com.google.firebase.** { *; }
-keep class com.google.firebase.** { *; }
-dontwarn com.google.firebase.**

• Same rule works on other devices

[MichaelVerdon]

Hi there, unfortunately there is not much we can do about this issue on Firebase side. This appears to be due to Huawei generally not supporting Google-Play-Services which seems to be set to soon over here: https://londondaily.com/huawei-s-harmonyos-reportedly-to-allow-google-play-services-interoperability-weibo-tipster-reveals You can encourage users to upgrade os versions to see if that will work. You can ask Huawei users to ensure they have manually installed google-play-services. Another site here states that we cannot https://www.three.co.uk/support/device-support/huawei-and-google-your-questions-answered#:~:text=The%20new%20Huawei%20P40%20Pro,web%20version%20of%20the%20app. As a work around, you can try use an alternative module for notifications and check for the device being Huawei. It is a bit strange to narrow it down due to conflicting information online but the general sentiment is that there are issues with Google-Play-Services and Huawei

To confirm this hypothesis, I would like to ask you to programmatically check if Huawei users have those issues as illustrated here https://stackoverflow.com/questions/79424490/react-native-and-expo-check-if-google-play-services-are-available

[vlack-coder]

Hi @MichaelVerdon , thanks for looking into this.

Can it be because of this function in the index.js because I use GMS check in the App.tsx file of the project

messaging().setBackgroundMessageHandler(async remoteMessage => {
    await notifee.requestPermission();
});

And I also noticed that from the stacktrace, the js runtime has not started and It happens in less than a sec into opening the app on the native side.
Moreso, it's also showing that it is from the FirebaseCrashlytics instantiation rather than messaging which needs the GMS.
and I also suppose that if users opens the app again it works because we couldn't have gotten the crashlytics data of the session that crashed. I might be wrong.

[MichaelVerdon]

Hey there, I really do not think it is due to this. I think it is quite clearly a device issue and if it crashes on startup, I think it confirms my findings that Google-Play-Services has issues on Huawei as that could explain the application crashing this soon if I am understanding you correctly. Here is an article by who I assume to be an engineer that details possible work arounds https://medium.com/@eamankyim/unraveling-the-mystery-why-huawei-phones-dont-support-firebase-and-its-impact-on-user-experience-72be2504ac75
In summary:

• You can try use the REST API which requires alot more development effort.
• Use HMS Core as an alternative.
• Warn users or prevent installs to Huawei devices (Unless its something not good to do on your end)
  Unfortunately we will not be able to do anything so I will be closing this. Thank you for your ticket and feel free to open another one if you have another issues 😄