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
In iOS, when opening or resuming the app, I'm calling OneSignal.Notifications.clearAll(); to clear the notifications and to reset the notifications badge count to Zero, but once a new notification is received the badge number shown is accumulated from the previous number instead of showing (1) as the notifications count.
Steps to reproduce?
1. Sent a number of notifications to the app (let's say 3).
2. Open/resume the app.
3. Call OneSignal.Notifications.clearAll(); once the app is opened/resumed.
4. Notifications and notification badge will be cleared.
5. Send a new notification to the app.
6. instead of showing (1) at the notification badge on app icon it will show (4).
What did you expect to happen?
Once notifications are cleared, the badge should be cleared, and when receiving a new notification the badge should show (1) not (previous notifications count + 1).
OneSignal Flutter SDK version
Release 5.2.2
Which platform(s) are affected?
iOS
Android
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What happened?
In iOS, when opening or resuming the app, I'm calling
OneSignal.Notifications.clearAll();
to clear the notifications and to reset the notifications badge count to Zero, but once a new notification is received the badge number shown is accumulated from the previous number instead of showing (1) as the notifications count.Steps to reproduce?
What did you expect to happen?
Once notifications are cleared, the badge should be cleared, and when receiving a new notification the badge should show (1) not (previous notifications count + 1).
OneSignal Flutter SDK version
Release 5.2.2
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: