You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 7, 2026. It is now read-only.
Hi, we recently discovered that triggerNotifications will not display at all when using alarmManager: { allowWhileIdle: true } (or the more recent alarmManager: { type: AlarmType.[any of the types] }) on Android 14, unless battery optimization is disabled for the app. It did work fine on previous Android versions even without disabling battery optimization. This was tested on both React-Native 0.72 and 0.73, and with @notifee/react-native version 7.8.0 and 7.8.2.
Can be reproduced by creating a new RN app from template (and running on a Android 14 device or emulator), installing notifee, creating a notification channel and scheduling a triggerNotification with a timestamp trigger with the alarmManager attribute set.
Getting the users to disable battery optimization would be ideal, but since it requires some work on the user's end we can't rely entirely on that. I suppose checking for whether battery optimization is enabled and only using the alarmManager when it isn't is the only real solution?
Are there any additional permissions or such that are required with Android 14, and is this issue well known?
Hi, we recently discovered that triggerNotifications will not display at all when using
alarmManager: { allowWhileIdle: true }(or the more recentalarmManager: { type: AlarmType.[any of the types] }) on Android 14, unless battery optimization is disabled for the app. It did work fine on previous Android versions even without disabling battery optimization. This was tested on both React-Native 0.72 and 0.73, and with@notifee/react-nativeversion 7.8.0 and 7.8.2.Can be reproduced by creating a new RN app from template (and running on a Android 14 device or emulator), installing notifee, creating a notification channel and scheduling a triggerNotification with a timestamp trigger with the alarmManager attribute set.
Getting the users to disable battery optimization would be ideal, but since it requires some work on the user's end we can't rely entirely on that. I suppose checking for whether battery optimization is enabled and only using the alarmManager when it isn't is the only real solution?
Are there any additional permissions or such that are required with Android 14, and is this issue well known?