Scheduling restart of crashed service [package-name]/io.invertase.firebase.messaging.ReactNativeFirebaseMessagingHeadlessService #8648
Unanswered
malekmajzoubHT
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, when i have an expo app with firebase messaging installed. This is only happening on android (I have Samsung A34 Android v 15)
Versions:
on app initialization i call
const { IOS, ANDROID } = RNCALLKEEP_CONSTANTS.CONFIG; RNCallKeep.registerPhoneAccount({ ios: { appName: IOS.appName }, android: ANDROID });
so the app is registered as a calling app on android.
When I receive an FCM message notification while the app is in a killed state and I open the app (by pressing th icon in home screen of phone and not from tapping notification), the app launches normally. However, when i kill the app, i see this in my logs
W ActivityManager: Scheduling restart of crashed service [package-name]/io.invertase.firebase.messaging.ReactNativeFirebaseMessagingHeadlessService in 11350ms for start-requested
and the app is stuck on native splash screen (JS code is not reached, i don't see any logs in App.tsx) on the next app launch and following launches. I have to wait a certain amount of time till I can launch the app again.
When I don't call registerPhoneAccount this error doesn't show and the app opens normally the following times.
Why does firebase messaging headless service crash happen only when the app is registered as a calling app and it is force closed?
Thank you for any help you can provide!
Beta Was this translation helpful? Give feedback.
All reactions