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

Badge not clean after open app #1411

Open
Marcuspo opened this issue Jul 25, 2022 · 6 comments
Open

Badge not clean after open app #1411

Marcuspo opened this issue Jul 25, 2022 · 6 comments

Comments

@Marcuspo
Copy link

Description:

In app, after i send one push, the badge not clean after.

Captura de Tela 2022-07-25 às 08 57 13

RPReplay_Final1658526972.MP4

Environment

  1. What version of the OneSignal React-Native SDK are you using?
    R: "^4.3.0"

  2. How did you add the SDK to your project (eg. npm)
    R: yarn

Steps to Reproduce Issue:

  1. Send one push
  2. Badge is incremented
  3. Open app
  4. Close app
  5. Send another push
  6. Badge not clean
@jkasten2
Copy link
Member

@Marcuspo There are few things that can cause the badge count internal counter to be reset back to 0. It requires the following to be setup correctly:

If you have an issue with the NSE or App Groups still after trying to debug you may want to also include onesignal-expo-plugin as this automatically sets these up for you.

@fabriciosautner
Copy link

Same problem

@manuhook
Copy link

manuhook commented Mar 7, 2023

I'm having the same problem on iOS since few weeks, it was working before.

@manuhook
Copy link

@jkasten2
We have check your recommandations but still no luck, the badge is no reseting back to 0 on a new notification as it should be : https://documentation.onesignal.com/docs/troubleshooting-ios#previous-push-notifications-disappear

The problem is happening since 1 month (no changes on the app notification source code),
we are using react-native-onesignal 4.4.1.
I guess the problem appeared after an iOS or Xcode update.

@fabriciosautner
Copy link

For us, it's been almost 2 years now that we have the same problem.
To date it has not been resolved.

@jaredswenson
Copy link

Any updates on this?

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

5 participants