Android: Silent error when displaying notification and maximum reached

Depending on the android version there is a maximum number of notifications that can be posted to the device. Sometimes 50 sometimes 24. Some manufacturers can even set a different number.

There is no way to query this value (MAX_PACKAGE_NOTIFICATIONS). An error is thrown natively but is not bubbled up to javascript when awaiting notifee.displayNotification, it fails silently.

Only solution I found so far is to get (await notifee.getDisplayedNotifications()).length; before and after calling displayNotification , then cancel a notification and retry after that.

Would be nice to avoid doing the get before and after and just have an error and handle it.

[mikehardy]

What do you think about posting the notification then post-checking the current displayed list to see if it actually went in? Then our API could at least indicate success or failure? Just brainstorming though, admittedly. Trying to see if there is any signal we could squeeze out

[mikehardy]

Interesting - it is hard to get a stacktrace because the assertion that it “silently throws” is incorrect - there is no throw, so there is no stacktrace. It’s silently dropping them, that’s different. (the link to the source was critical in examining this - thanks)

I’m not sure how to handle this then, other than your method of getting the list first, posting, then checking the list again. That should work but there’s the chance the user interacts with a notification (clearing one or more) or that the app in another thread does something (javascript is not multi-threaded but firebase-android-sdk is and if you receive an FCM with a notification block it may attempt to post). So just doing a count is not sufficient I think

I have not worked in this repo in a while so my memories are growing vague but I think there is the idea of a notification ID, it should be able to verify the specific ID you expect is in the list after posting it?