Hi,

I noticed that cancelTriggerNotifications sometimes returns before the scheduled notifications are removed from the database. So far I only noticed it on Android.

In the test below, the number of scheduled notification is not always zero after notifee.cancelTriggerNotifications returned.

await notifee.cancelTriggerNotifications()
console.log('number of scheduled notification:', (await notifee.getTriggerNotifications()).length) // not always 0

In our app, we cancel all notifications before scheduling a new one. The issue cases a race condition. Sometimes the first few notifications we scheduled are removed unexpectedly by the ongoing cancelTriggerNotifications. The example below shows what we are doing.

await notifee.cancelTriggerNotifications()
await notifee.createTriggerNotification(...)  // this notification could be removed 

I looked into the native code, do you think this might be the issue that the deletion occurs in the onSuccess callback?

Many thanks,
Yupeng