[🐛] Bug Report Title - Data only notifications on android don't arrive when app is closed (EXPO) #8443
Comments
MichaelVerdon
added
platform: android
plugin: messaging
|
Hey there, can you show me a usage example of how you are using the background handler? |
Here is my handler at the top of my root setBackgroundMessageHandler(
messaging,
async (message: FirebaseMessagingTypes.RemoteMessage) => {
if (!message.notification) {
try {
await notifee.incrementBadgeCount();
await handleBackgroundMessage(message);
} catch (error) {
console.error("Error displaying notification:", error);
}
}
return Promise.resolve();
}
);As instructed in the docs, always return a resolved promise.
|
|
@MichaelVerdon , are there other informations you'll need on this?. It's a bug that needs to be fixed on my end 🙏 |
OgDev-01
changed the title
|
Hi there, i am currently investigating it. My testing app refused to work yesterday but it is all good today. 😄 |
I reformatted the JSON you send in the FCM so it was readable and I could scan for that key on a hunch. I don't see it |
|
Hey there, I did receive a notification whilst the app was in a terminated state and it opened the app. It did not work until I put this in my AndroidManifest (registering the service): https://firebase.google.com/docs/cloud-messaging/android/client And you need to use this method getInitialNotification: https://rnfirebase.io/reference/messaging#getInitialNotification I will warn you that it has been a bit flaky and I've observed messaging can be flaky with these things across other platforms making me think if it is an Android-Firebase native issue |
|
Also make sure there is a notification in your payload, I don't think data-only works. What purpose do you need it to be data only? |
That's not true - data-only on android works fine. iOS is very problematic and at the whim of the OS as to whether it will deliver or not - it will sometimes, enough to trick you into thinking it's reliable when it isn't - but android data-only works great in my experience |
You shouldn't need to do that, during AndroidManifest merge, that is added by the android gradle build process into the final combined AndroidManifest for the app, coming from this chunk here: To put that in the app-level AndroidManifest is to basically duplicate it - if you open an app with react-native-firebase messaging integrated and check the "Combined" AndroidManifest tab you should see it in there, merged in automatically I've never had to manually put this in my apps - so I suspect a test methodology error somehow when it had a negative delivery test result without it |
|
Thanks for clarification @mikehardy I still think it might be worth trying anyways as I managed to get it to work on my end doing that but on the other hand, I don't think I needed to do that with FlutterFire 🤔 |
Honestly, i think the formatted payload looks different from the initial. This is the correct payload the app receives{
"originalPriority": 1,
"priority": 1,
"sentTime": 1744117869665,
"data": {
"notifee": "{\"title\":\"string\",\"body\":\"string\",\"data\":{\"additionalProp1\":\"string\",\"additionalProp2\":\"string\",\"additionalProp3\":\"string\"},\"deepLink\":\"string\",\"imageUrl\":\"string\",\"type\":\"MEDICATION_REMINDER\"}",
"type": "MEDICATION_REMINDER",
"body": "string",
"title": "string",
"additionalProp3": "string",
"additionalProp1": "string",
"additionalProp2": "string",
"imageUrl": "string"
},
"from": "688826572618",
"messageId": "0:1744117869689285%2bc11c71cad56011",
"ttl": 259200,
"collapseKey": "string"
}Our api uses the firebase admin sdk in java, and we are setting the priority for every data message payload that is sent over. |
|
This is our snippet on the backend using the firebase admin private AndroidConfig buildAndroidConfig(PushNotificationRequest request) {
return AndroidConfig.builder()
.setPriority(AndroidConfig.Priority.HIGH)
.setCollapseKey(request.getTitle())
.setDirectBootOk(true)
.setTtl(259200000)
.build();
}
private ApnsConfig buildApnsConfig(PushNotificationRequest request) {
ApnsConfig.Builder builder = ApnsConfig.builder();
builder.setAps(
Aps.builder()
.setContentAvailable(true)
.build());
if (request.getDeepLink() != null) {
builder.putHeader("link", request.getDeepLink());
}
Map<String, String> apnsHeaders = new HashMap<>();
apnsHeaders.put("apns-priority", "5");
apnsHeaders.put("apns-push-type", "background");
builder.putAllHeaders(apnsHeaders);
return builder.build();
}this line I all looks like we are doing all the needful 😟 , but it just seem not to work on android. I appreciate the efforts and quick response from the team 👍 . Any idea what i'm doing wrong? @mikehardy |
Nope sorry, out of ideas. You might try https://dontkillmyapp.com/, make sure you don't have power saving on, check |
Leaving this here for anyone who gets into same situation.I was able to solve the problem by avoiding the problem all together 😄 . I initially opted for data-only messages due to some limitations on IOS > 17 #7548. But fixing it with the walk around introduced this issue on android. What i ended up doing?I still sticked to my data only message payload, but this time just for IOS. and i added notification key to the payload for android, and this solved my issue. Thanks @mikehardy and @MichaelVerdon for the support 👍 |
|
interesting - usually it is the other way around, data-only works well for android in my experience but on ios they are problematic I want to emphasize that in my experience on iOS data-only messages will show up for you, the developer, while you are testing with your device plugged in in the app you use all the time (since you are the developer). But iOS is very very very stingy with the power budget that it will give apps in response to messages, and if the device is too hot, low on battery at all, background refresh is off, or low power mode is on, or the user doesn't use your app all the time you will not get the FCM delivered to the iOS app as data-only Most people opt for notification block on iOS for this reason |
Thank you for this insight... I'll keep a close watch on this behaviour and also try a POC on a separate app to see how opting to the notification block turns out on IOS. Will update my findings here from time to time |
Issue
Describe your issue here
I'm using
@react-native-firebase/messagingwith@notifee/react-nativeto handle notifications on my app... But android notifications don't arrive on devices when the app is closed.Key things to note
I did some research and bumped into #1238 but the conversations there seems quite old and i'm using Expo managed workflow.
Message Payload
{ "android": { "asForegroundService": false, "autoCancel": true, "badgeIconType": 2, "channelId": "reminders", "chronometerDirection": "up", "circularLargeIcon": false, "colorized": false, "defaults": [ -1 ], "groupAlertBehavior": 0, "groupSummary": false, "importance": 3, "largeIcon": "https://golivwell-s3-bucket.s3.eu-central-1.amazonaws.com/c1a8c098-3b2c-428a-ba02-8462cac2ca6b_products.jpg", "lightUpScreen": false, "localOnly": false, "loopSound": false, "ongoing": false, "onlyAlertOnce": false, "showChronometer": false, "showTimestamp": true, "smallIcon": "ic_launcher", "timestamp": 1743770458521, "visibility": 0 }, "body": "I did this again version 2", "data": { "notifee": { "body": "I did this again version 2", "data": "[Object]", "deepLink": "string", "imageUrl": "https://golivwell-s3-bucket.s3.eu-central-1.amazonaws.com/c1a8c098-3b2c-428a-ba02-8462cac2ca6b_products.jpg", "title": "Hello from swagger", "type": "MEDICATION_REMINDER" } }, "id": "zWNs9jm0ZwW1IYXxWuvZ", "title": "Hello from swagger" }Project Files
Javascript
Click To Expand
package.json:{ "name": "Golivwell", "version": "1.0.4", "private": true, "main": "expo-router/entry", "scripts": { "start": "cross-env EXPO_NO_DOTENV=1 expo start", "prebuild": "cross-env EXPO_NO_DOTENV=1 pnpm expo prebuild", "android": "cross-env EXPO_NO_DOTENV=1 expo run:android", "ios": "cross-env EXPO_NO_DOTENV=1 expo run:ios", "doctor": "npx expo-doctor", "preinstall": "npx only-allow pnpm", "start:staging": "cross-env APP_ENV=staging pnpm run start", "prebuild:staging": "cross-env APP_ENV=staging pnpm run prebuild", "android:staging": "cross-env APP_ENV=staging pnpm run android", "ios:staging": "cross-env APP_ENV=staging pnpm run ios", "start:production": "cross-env APP_ENV=production pnpm run start", "prebuild:production": "cross-env APP_ENV=production pnpm run prebuild", "android:production": "cross-env APP_ENV=production pnpm run android", "ios:production": "cross-env APP_ENV=production pnpm run ios", "build:development:ios": "cross-env APP_ENV=development EXPO_NO_DOTENV=1 eas build --profile development --platform ios", "build:development:android": "cross-env APP_ENV=development EXPO_NO_DOTENV=1 eas build --profile development --platform android", "build:staging:ios": "cross-env APP_ENV=staging EXPO_NO_DOTENV=1 eas build --profile staging --platform ios", "build:staging:android": "cross-env APP_ENV=staging EXPO_NO_DOTENV=1 eas build --profile staging --platform android", "build:production:ios": "cross-env APP_ENV=production EXPO_NO_DOTENV=1 eas build --profile production --platform ios", "build:production:android": "cross-env APP_ENV=production EXPO_NO_DOTENV=1 eas build --profile production --platform android", "update:prod": "cross-env APP_ENV=production eas update --clear-cache --channel production --message \"Automated update to prod\"", "update:staging": "cross-env APP_ENV=staging eas update --clear-cache --channel staging --message \"Automated update to staging\"", "postinstall": "patch-package && husky install", "app-release": "cross-env SKIP_BRANCH_PROTECTION=true np --no-publish --no-cleanup --no-release-draft --branch beta", "version": "pnpm run prebuild && git add .", "lint": "eslint . --ext .js,.jsx,.ts,.tsx", "lint:fix": "eslint . --ext .js,.jsx,.ts,.tsx --fix", "format": "prettier --write .", "type-check": "tsc --noemit", "lint:translations": "eslint ./src/translations/ --fix --ext .json", "test": "jest", "test:ci": "pnpm run test --coverage", "test:watch": "pnpm run test --watch", "install-maestro": "curl -Ls 'https://get.maestro.mobile.dev' | bash", "e2e-test": "maestro test .maestro/ -e APP_ID=com.obytes.development" }, "dependencies": { "@expo-google-fonts/poppins": "^0.2.3", "@expo/metro-runtime": "^3.2.3", "@gluestack-ui/accordion": "^1.0.6", "@gluestack-ui/nativewind-utils": "^1.0.23", "@gluestack-ui/overlay": "^0.1.15", "@gluestack-ui/popover": "^0.1.37", "@gluestack-ui/toast": "^1.0.7", "@gorhom/bottom-sheet": "^4.6.3", "@hookform/resolvers": "^2.9.11", "@legendapp/motion": "^2.3.0", "@notifee/react-native": "^9.1.8", "@react-native-community/datetimepicker": "8.0.1", "@react-native-firebase/app": "^21.12.0", "@react-native-firebase/messaging": "^21.12.0", "@react-navigation/bottom-tabs": "^6.5.20", "@react-navigation/material-top-tabs": "^6.6.2", "@react-navigation/native": "^6.1.17", "@react-navigation/native-stack": "^6.9.26", "@shopify/flash-list": "1.6.4", "@tanstack/react-query": "^5.37.1", "app-icon-badge": "^0.0.15", "axios": "^1.7.1", "expo": "~51.0.39", "expo-build-properties": "~0.12.5", "expo-constants": "~16.0.2", "expo-dev-client": "~4.0.29", "expo-device": "^6.0.2", "expo-file-system": "~17.0.1", "expo-font": "~12.0.10", "expo-image": "~1.13.0", "expo-image-picker": "^15.1.0", "expo-linear-gradient": "~13.0.2", "expo-linking": "~6.3.1", "expo-localization": "~15.0.3", "expo-notifications": "~0.28.19", "expo-router": "~3.5.24", "expo-sharing": "~12.0.1", "expo-splash-screen": "0.27.7", "expo-status-bar": "~1.12.1", "expo-system-ui": "~3.0.7", "expo-updates": "~0.25.28", "expo-web-browser": "~13.0.3", "gifted-charts-core": "^0.1.30", "i18next": "^22.5.1", "lodash.memoize": "^4.1.2", "moti": "^0.28.1", "nativewind": "^4.0.36", "react": "18.2.0", "react-dom": "18.2.0", "react-error-boundary": "^3.1.4", "react-hook-form": "^7.51.4", "react-i18next": "^12.3.1", "react-native-avoid-softinput": "^4.0.2", "react-native-calendars": "^1.1306.0", "react-native-chart-kit": "^6.12.0", "react-native-css-interop": "0.0.36", "react-native-flash-message": "^0.4.2", "react-native-gesture-handler": "~2.16.2", "react-native-gifted-charts": "^1.4.29", "react-native-image-picker": "^7.1.2", "react-native-keyboard-controller": "^1.14.4", "react-native-marked": "^6.0.5", "react-native-mmkv": "2.6.3", "react-native-otp-entry": "^1.7.0", "react-native-pager-view": "6.3.0", "react-native-permissions": "^4.1.5", "react-native-qrcode-svg": "^6.3.2", "react-native-reanimated": "~3.10.1", "react-native-restart": "0.0.27", "react-native-safe-area-context": "4.10.5", "react-native-screens": "~3.31.1", "react-native-svg": "15.2.0", "react-native-tab-view": "^4.0.1", "react-native-web": "~0.19.11", "react-native-webview": "13.8.6", "react-query-kit": "^3.3.0", "tailwind-variants": "^0.1.20", "terra-react": "^1.6.15", "zod": "^3.23.8", "zustand": "^4.5.2", "react-native": "0.74.5" }, "devDependencies": { "@babel/core": "^7.24.5", "@commitlint/cli": "^17.8.1", "@commitlint/config-conventional": "^17.8.1", "@dev-plugins/react-navigation": "^0.0.6", "@dev-plugins/react-query": "^0.0.6", "@expo/config": "~9.0.2", "@react-native-community/eslint-config": "^3.2.0", "@testing-library/jest-dom": "^5.17.0", "@testing-library/react-native": "^12.5.0", "@types/i18n-js": "^3.8.9", "@types/jest": "^29.5.12", "@types/lodash.memoize": "^4.1.9", "@types/react": "~18.2.79", "@types/react-test-renderer": "^18.3.0", "@typescript-eslint/eslint-plugin": "^5.62.0", "@typescript-eslint/parser": "^5.62.0", "babel-plugin-module-resolver": "^5.0.2", "clsx": "^2.1.1", "cross-env": "^7.0.3", "date-fns": "^3.6.0", "dotenv": "^16.4.5", "eslint": "^8.57.0", "eslint-plugin-i18n-json": "^4.0.0", "eslint-plugin-simple-import-sort": "^10.0.0", "eslint-plugin-tailwindcss": "^3.15.2", "eslint-plugin-testing-library": "^6.2.2", "eslint-plugin-unicorn": "^46.0.1", "eslint-plugin-unused-imports": "^2.0.0", "husky": "^8.0.3", "jest": "^29.7.0", "jest-environment-jsdom": "^29.7.0", "jest-expo": "~51.0.4", "jest-junit": "^16.0.0", "lint-staged": "^13.3.0", "metro-babel-register": "^0.73.10", "np": "^7.7.0", "prettier": "^2.8.8", "react-test-renderer": "^18.3.1", "tailwind-merge": "^2.5.2", "tailwindcss": "3.3.2", "ts-jest": "^29.1.2", "typescript": "^5.3.3" }, "repository": { "type": "git", "url": "git+https://github.com/integrated-wellness-inc/livwell-mobile-app.git" }, "packageManager": "[email protected]", "osMetadata": { "initVersion": "6.1.0" } }firebase.jsonfor react-native-firebase v6:# N/AiOS
Click To Expand
ios/Podfile:# N/AAppDelegate.m:Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settingsjetifier=truefor Android compatibility?jetifierfor react-native compatibility?android/build.gradle:android/app/build.gradle:android/settings.gradle:MainApplication.java:// N/AAndroidManifest.xml:Environment
Click To Expand
react-native infooutput:react-native-firebaseversion you're using that has this issue:e.g. 5.4.3Firebasemodule(s) you're using that has the issue:e.g. Instance IDTypeScript?Y/N&VERSIONReact Native FirebaseandInvertaseon Twitter for updates on the library.The text was updated successfully, but these errors were encountered: