-
Notifications
You must be signed in to change notification settings - Fork 365
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]: preventDefault not working as expected if app relaunch within 30s #1919
Comments
@Harris-Cww thanks for reaching out! We're working on reproducing this and will get back to you as soon as possible. |
any update on this issue? I'm currently saving the notification id and compare it every time i receive push notification again, which is kinda troublesome. hope to have some better solution, thanks |
@jennantilla |
Any news on it? Facing the same issue |
I'm also facing the same issue. The symptoms of the following ticket may be similar. |
Hello @jennantilla |
What happened?
preventDefault doesn't prevent notification from reappear if user relaunch within 30 sec since NotificationGenerationProcessor.doWork() has a 30 sec window to wait if preventDefault is called before actually calling markNotificationAsDismissed() to mark the notification as shown.
Steps to reproduce?
What did you expect to happen?
preventDefault should mark the notification as shown immediately and will not show again after app relaunch
OneSignal Android SDK version
release 5.0.4
Android version
13
Specific Android models
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: