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

[Bug]: Previous received notification is showing up again when app is opened next time. #636

Closed
3 tasks done
Jos-Sea opened this issue Jan 10, 2023 · 6 comments
Closed
3 tasks done

Comments

@Jos-Sea
Copy link

Jos-Sea commented Jan 10, 2023

What happened?

I dismissed the notification I received from the notification panel but the same dismissed notification appeared again when the app was opened. And was also showing the notification received past time. Example as 5h.

Steps to reproduce?

1. when notification receive dismiss from notification panel
2. close the app and don't use it for some time
3. open the app again
4. now will see the previous dismissed notification is showing up again.

What did you expect to happen?

The expected result should be dismissed notification should not show again when user open the app next time.

OneSignal Flutter SDK version

3.3.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
@brismithers
Copy link
Contributor

Hi @Jos-Sea , I haven't been able to reproduce this unfortunately. Can you confirm this is both an Android and an iOS issue?

@Jos-Sea
Copy link
Author

Jos-Sea commented Feb 2, 2023

Hi @brismithers, The issue has only been confirmed to reproduce on the Android platform.

@alabiboo
Copy link

Hi @Jos-Sea , I have the same problem. did you find a solution that could help me too?

@NOTtheKRish
Copy link

Hello @Jos-Sea , I too have the same problem... Is there any solution to solve this??

@foxfoxfox789
Copy link

Got the same issue, any help ?

@jennantilla
Copy link
Contributor

Hello there everyone! Apologies that this issue has gone stale. Since the original report of this problem, we have released a new version of our SDK with many improvements and enhancements. Please update to our latest release (see migration guide) and if you are still having any trouble, we encourage you to open a new ticket so we can renew investigation. Thanks!

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

6 participants