Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect number returned by getBadgeCount() #987

Open
tao-qian opened this issue Feb 9, 2024 · 6 comments
Open

Incorrect number returned by getBadgeCount() #987

tao-qian opened this issue Feb 9, 2024 · 6 comments

Comments

@tao-qian
Copy link

tao-qian commented Feb 9, 2024

Our iOS app receives push notification with a badge payload, which would change the badge count on the app without going through our app code. However, when calling getBadgeCount() after opening the app, the returned number is still 0. At the same time, calling setBadgeCount(0) also won't clear the badge on the app.

This is not reproducible when the notification is received while the app is in foreground, in which case the badge count would be incremented by us, instead of the system code.

It seems like the system badge count is out of sync with the "internal notifee badge count". Has anyone else run into similar problems?

Copy link

github-actions bot commented Mar 8, 2024

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@tao-qian
Copy link
Author

tao-qian commented Mar 8, 2024

bump

Copy link

github-actions bot commented Apr 5, 2024

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@tao-qian
Copy link
Author

tao-qian commented Apr 6, 2024

bump

Copy link

github-actions bot commented May 4, 2024

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

@tao-qian
Copy link
Author

tao-qian commented May 4, 2024

bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant