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 has been archived by the owner on Jun 19, 2018. It is now read-only.
It seems that the plugin automatically resets the badge to zero each time the app becomes active (at least on iOS). How can I prevent this behavior if I want to keep the badge at its current value even if the app becomes active ?
A typical use case would be to handle a badge counter of unread messages (in the same manner than the Mail.app).
I don't want to modify and keep an out-of-sync version of the native code in my project repository that might break each time I update the plugin.
Could it be possible to benefit from the "resume" device event in the JS layer and reset the badge here only if needed ?
The text was updated successfully, but these errors were encountered:
@kumaresan-cgvak I don't think it is a bug. It makes sense to reset the badge each time the app becomes active, but when you need to avoid it, it's hard to come up with a workaround.
@nashfive if the App developer wish to reset during this scenario, then he could reset it by using "pushNotification.setApplicationIconBadgeNumber(successCallback, errorCallback, "0");" during app resume status. Which adds more flexibility to developer.
It seems that the plugin automatically resets the badge to zero each time the app becomes active (at least on iOS). How can I prevent this behavior if I want to keep the badge at its current value even if the app becomes active ?
A typical use case would be to handle a badge counter of unread messages (in the same manner than the Mail.app).
I don't want to modify and keep an out-of-sync version of the native code in my project repository that might break each time I update the plugin.
Could it be possible to benefit from the "resume" device event in the JS layer and reset the badge here only if needed ?
The text was updated successfully, but these errors were encountered: