expo: expo-notifications scheduleNotification is not working as expected in devices

If someone is struggling with the same issue : for me the solution was to upgrade my expo SDK from 38 to 39. I think it is supposed to be working with 38 version but for some reason it doesn’t. As soon as I upgraded it starts working like a charm.

hi @ltsharma, it sounds like maybe your scheduled notifications are getting a little mixed up. What you may want to do is build in some sort of debugging workflow where you can check on what notifications you have scheduled with Notifications.getAllScheduledNotificationsAsync. I’ve tested daily notification triggers myself, e.g.

await Notifications.scheduleNotificationAsync({
      identifier: "myidentifer",
      content: {
        title: "You've got mail! 📬",
        body: "Here is the notification body",
        data: { data: "goes here" },
      },
      trigger: {
        hour: 12,
        minute: 15,
        repeats: true,
      },
    });

and haven’t seen any of the behavior you’re describing

Finally, yes. if battery optimization is turned on in xaomi & onplus devices were not getting local daily notifications. i turned it off in app setting now its working properly. so my next questions,

• is it expected behavior?
• if yes, how to disable it by default? (i got soln, but that will scares user about battery optimization by showing it in model while allowing it).
• if No, how to solve it?

Yep of course 😃 You can find bellow a simple component example to create a notification from what i did. I didn’t try it but it should work, tell me if not :

First => don’t forget to add this line in your app.json under the android object : "useNextNotificationsApi": true,

Then : ` import * as Notifications from ‘expo-notifications’; import * as Permissions from ‘expo-permissions’;

   // don't forget this notificationHandler
   Notifications.setNotificationHandler({
    handleNotification: async () => ({
       shouldShowAlert: true,
       shouldPlaySound: false,
       shouldSetBadge: false,
    }),
 });

 class Notification extends React.Component {
  constructor(props) {
    super(props)
    this.state = {
        time: Date.now(), // change it by the time you need
        title: 'title',
        body: 'content'
     }
 }

async componentDidMount() {
    const { status: existingStatus } = await Permissions.getAsync(Permissions.NOTIFICATIONS);
    let finalStatus = existingStatus;
    if (existingStatus !== 'granted') {
      const { status } = await Permissions.askAsync(Permissions.NOTIFICATIONS);
      finalStatus = status;
    }
    if (finalStatus !== 'granted') {
      alert(this.context.translate(this.context.translations, 'notification.missing_permission'));
      return;
    }
}

onSubmit() {
        Notifications.scheduleNotificationAsync({
            content: {
            title: this.state.title,
            body: this.state.body,
            },
            trigger: {
                // every day at the same time
                hour: date.getHours(),
                minute: date.getMinutes(),
                repeats: true
            }
        });
 }

render() {
    <View style={{flex: 1}}>
       <Button title="Try me" color="#841584" onPress={() => this.onSubmit()}></Button>
    </View>
}
}

`

@ltsharma : I am also using Daily and Scheduled Local Notifications and having the same problems on Android where they work when battery optimization is turned off.

Is there a better solution to this?

Will this happen even with Push Notifications as well? I found this on OneSignal website : https://documentation.onesignal.com/docs/notifications-show-successful-but-are-not-being-shown#low-power-energy-saving

@ltsharma - android device oems have full control over what they want to do to the operating system on their devices. some may make strange changes like this that impact notifications and create inconsistency in the android ecosystem because they think it will be a good feature/improvement for their customer. you could detect the device type and warn people in the case of devices that you believe have this issue, if you like.

@cruzach , it’s not actually about troubleshooting. After intensive observations, found that this behavior is happening only in custom UIs like miui (xiaomi), emui (one plus) & one UI (Samsung). Nokia appears to be working fine with pure android. Now i’m trying with disabling battery optimization off in app setting, i will update the status.