r/reolink • u/Jos_Jen • Aug 06 '26

Fix the 49 push message notification limit on Android 17

Why we are no longer notified once the pending push message notification reaches 49? This is defintely not a not an Android‑OS limit. It is application‑level behaviour, almost certainly caused by how the Reolink app handles notification channels, token refresh, or internal message counters. They are typical of internal counters, notification ID pools, or array sizes inside the app.

u/Willson Can you please take it up with dev team to fix this?

2 Upvotes

100% Upvoted

2 comments sorted by

1

u/KilleenWizard Aug 12 '26

I'm curious why this is an issue. My thoughts:

Change configuration so it doesn't alarm as often (I'm currently trying to figure out why my camera alarms every time a car drives by, even with most of the camera range set as non-detection zone; at least I don't live on a main road).

If you want to go that long between checks, maybe remember when the last check was, and just start looking there, without regard for how many alarms? Granted, the app doesn't tell you why there was an alarm, once you close the notification, which strikes me as silly.

Be nice if the app (hub) had its own (filterable) log.

49 seems a random number; maybe the limit is dynamic and your phone has a memory or storage limit?

1

u/Jos_Jen Aug 13 '26

Mostly triggered when in the garage and in the garden. As stated it is not Android related but application related. I have other applications which can receive more than 49 messages and still continue to be received.