-
Notifications
You must be signed in to change notification settings - Fork 892
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
Android Edge: This site has been updated in background #2482
Comments
Thanks for reporting, @kanadaj. I was able to get the same behavior and indeed, it only occurs in Edge.
|
Hi @rommelpe, I found this issue through Google because I switched to Edge for Android but noticed website notifications not working anymore like they should. Are there any updates on this? |
This happens on Windows, too, if your Edge instances are all closed. I believe this might be an intended behavior of the browser. Firefox for example chooses to not show push notifications until the user opens the browser again. Seems like different design choices, not an error with the SDK 🤔 |
Same problem with FCM REST. Android Edge displays notification "This site was updated in the background" . Notification does not interact, does not open the provided link, no icon is shown. |
Same problem. I'm getting "this site has been updated in the background". Also not receiving message in onMessage. I'm using Reac.js Any one can help? |
@Vijayakumarktm is this issue on Android Edge as well? If so, can you add the following details
This issue hadn't been updated in since 2020 so I want to confirm it's still the same issue. Also, would you be able to provide a minimal repo where this issue can be reproduced? |
@dwyfrequency I haven't even seen push notifications in Edge lately tbh, so I'm not certain that it even works anymore at all. I'm on Android 13 and Edge 114.0.1823.61 (And yes, notifications are enabled for Edge) |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
Relevant Code:
We use the following Service Worker:
This works perfectly fine in Chrome, but strangely enough Edge doesn't seem to receive the notification payload.
The text was updated successfully, but these errors were encountered: