Replies: 8 comments 29 replies
-
|
I think you'll find interesting information in the log output from |
Beta Was this translation helpful? Give feedback.
-
|
@mikehardy - Thank you for taking the time to respond. Over the last 2 days, I spent my time analyzing the adb logcat with different combinations, but wasn't able to get much except that the Headless task is not registered - which is probably owing to my placing the setbackgroundhandler in the wrong location. But beyond index.js & root layout, I am not able to think of any other place to put it in an Expo Router based app. I have scoured the internet for weeks & haven't found any good direction on this. Here are the excerpts from logcat of what I beleive is relevant with the key items I saw in bold . Any pointers to helping me use the wonderful rnfirebase in Expo Router based apps will be very helpful. Thank you.
02-07 22:10:17.652 2622 2763 I ActivityManager: Start proc 885:com.myownapp.app/u0a493 for broadcast {com.myownapp.app/io.invertase.firebase.messaging.ReactNativeFirebaseMessagingReceiver} SetbackgroundHandler is in the _layout.js (RootLayout): 02-07 21:40:31.722 1200 1267 I ActivityManager: Start proc 22766:com.myownapp.app/u0a346 for broadcast {com.myownapp.app/io.invertase.firebase.messaging.ReactNativeFirebaseMessagingReceiver} |
Beta Was this translation helpful? Give feedback.
-
|
same problem |
Beta Was this translation helpful? Give feedback.
-
|
same problem. do you already have a solution? |
Beta Was this translation helpful? Give feedback.
-
|
Same problem. Also interesting: Production builds crash after the splash screen when the listener is implemented, prebuilds work fine though! |
Beta Was this translation helpful? Give feedback.
-
|
I created index.ts in the root directory, and it worked index.ts i also remove the "main: expo-router/entry" inside the package.json |
Beta Was this translation helpful? Give feedback.
-
|
How do you send the notification? |
Beta Was this translation helpful? Give feedback.
-
|
Over the fcm rest api: |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that @coyksdev solution worked. I created new index.ts entry file & changed package.json main entry to "src/index.ts" |
Beta Was this translation helpful? Give feedback.
-
|
Which version of expo file based routing are you using? |
Beta Was this translation helpful? Give feedback.
-
Currently on 3.5.17 |
Beta Was this translation helpful? Give feedback.
-
|
it should be in your root dir |
Beta Was this translation helpful? Give feedback.
-
|
I can try |
Beta Was this translation helpful? Give feedback.
-
|
This repo contains a template version of my project based on your last suggestion. |
Beta Was this translation helpful? Give feedback.
-
|
update: when sending notifications via the fcm test notifications tool the message arrives but the handler still throws an error. I honestly don't really know what I should do next. |
Beta Was this translation helpful? Give feedback.
-
|
Did u guys find a solution to this? what exactly is happening in the index.ts file? Edit: index.ts and remove main from and also i did place my Root component as default export, not sure if it changes anything: app/_layout.tsx Background message handler triggered successfully from the Quit State on standalone Android build after that, now I just have to figure how to create a notification from there. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Are you using file based routing of the expo router? |
Beta Was this translation helpful? Give feedback.
-
|
same problem |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Have a solution that works perfectly - for ANDROID only. I don't understand it as well as some of you might (just a hobby developer), but let me share the Working Solution & what I think is the issue The issue seems to be that we need to register these notifee listeners outside the App Context. However, with Expo Router there's nothing like registering the Root component & so no way for us to register these listeners outside the App Context. The solution lay somewhere in the Expo documentation which said that we can access App Context in a certain way. So the final solution that worked for me was:
Now your notifee background listener will work in the Quit state too. Hurray ! I have tried this & it works perfectly. |
Beta Was this translation helpful? Give feedback.
-
|
I used you approach ans still don't receive any push notification when on quit mode aka app completely closed. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to use RNFirebase to handle notifications in an Expo app using Expo Router V2. I am using a EAS Development Build and I am using an Android device to test. My Project structure mimics the standard Expo Tabs template - https://github.com/expo/expo/tree/main/templates/expo-template-tabs
What Works ?
The RNFirebase Notif handling works perfectly both in Foreground & Background mode.
What does NOT work ?
Notification is not handled when the App is Quit. I have tried a simple API hit and the use of Notifee to show a notification in the Background Message Handler.
Note that the RNFirebase works in Foreground & Background mode well. It's only Quit mode that does nothing. So the message handling code doesn't seem to be an issue.
Any help / pointers to what will help me get RNFirebase to work with Expo Router V2 when the app is Quit ?
Beta Was this translation helpful? Give feedback.
All reactions