🔥 [🐛] Android Repeatedly crashing when receiving messages in a background or quit state - complains of no WAKE_LOCK permissions. about react-native-firebase HOT 2 OPEN

Does this still happen if you use current releases? They bring in new underlying firebase-android-sdk which may solve this

    "@react-native-firebase/app": "18.2.0",
    "@react-native-firebase/messaging": "18.2.0",

Very strange that the error would happen despite this in your AndroidManifest.xml

    <uses-permission
        android:name="android.permission.WAKE_LOCK"
        tools:node="replace" />

...I don't understand that a bit. I'd try a brand-new react-native app with a clean integration on messaging as a throw-away example and see if it still happens.

I maintain a build-demo script that you might be able to use as a starter and then just delete all the modules you don't care about https://github.com/mikehardy/rnfbdemo/blob/main/make-demo.sh

from react-native-firebase.

To be slightly more clear - without a reproduction this likely won't receive more attention. Native messaging is one of the main reasons people use react-native-firebase vs just using firebase-js-sdk, and Android 13 has been out quite a while, including on my personal phones with my production app, and it does not crash. No one else is reproducing this

from react-native-firebase.