Open mikkeldanielsen opened 12 months ago
YES, DEFINITELY!
even the tiny hint that's there is CRYPTIC AS FUCK: "BackgroundMessaging from react-native-firebase-(Optional)(Android-only)-Listen-for-FCM-messages-in-the-background)."
like, use a full sentence... what is optional, how...all the things. this is a MASSIVE hole where a concrete example is needed. I'm 5 days of research on this and totally stuck.
I mean, I appreciate the free code, just the frustration at this one hole is so huge :)
Using same FCM in the IOS, how to backtoForeground the app?
Help needed
[x] I've checked the example to reproduce the issue.
Reproduced on:
Description
The headless task RNCallKeepBackgroundMessage for android handles calls from the native dialer. Calls from the native dialer on iOS work like a charm. The app launches and the listener "didLoadWithEvents" has the call data.
On Android RNCallKeepBackgroundMessage is fired and I can start a call, but the headless task is destroyed before I can register if the call is active or failed. How do you cope with calls from the native dialer on Android? I can't find any documentation for RNCallKeepBackgroundMessage.
Versions