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

Android Edge: This site has been updated in background #2482

Open
kanadaj opened this issue Dec 30, 2019 · 7 comments
Open

Android Edge: This site has been updated in background #2482

kanadaj opened this issue Dec 30, 2019 · 7 comments

Comments

@kanadaj
Copy link

kanadaj commented Dec 30, 2019

[REQUIRED] Describe your environment

  • Operating System version: Android 10 QQ1B.191205.011
  • Browser version: Edge 42.0.4.4062
  • Firebase SDK version: 7.6.1
  • Firebase Product: messaging

[REQUIRED] Describe the problem

Steps to reproduce:

  • Set up Service Worker with the default non-GCM JS
  • Send notification
  • Chrome desktop gets the notification as expected
  • Android Chrome gets the notification as expected
  • Edge shows "This site was updated in the background"

Relevant Code:

We use the following Service Worker:

importScripts('https://www.gstatic.com/firebasejs/7.6.1/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/7.6.1/firebase-analytics.js');
importScripts('https://www.gstatic.com/firebasejs/7.6.1/firebase-messaging.js');
firebase.initializeApp({
    apiKey: "...",
    authDomain: "...",
    projectId: "...",
    messagingSenderId: "...",
    appId: "...",
});
const messaging = firebase.messaging();

This works perfectly fine in Chrome, but strangely enough Edge doesn't seem to receive the notification payload.

@rommelpe
Copy link

rommelpe commented Jan 6, 2020

Thanks for reporting, @kanadaj. I was able to get the same behavior and indeed, it only occurs in Edge.

edge-notif
I created a bug (b/147214252) internally, and progress updates will be posted here as well. Thanks.

@woutf
Copy link

woutf commented Jun 5, 2020

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?

@hdoro
Copy link

hdoro commented Oct 20, 2020

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 🤔

@ergec
Copy link

ergec commented Oct 23, 2020

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.

@Vijayakumarktm
Copy link

Same problem. I'm getting "this site has been updated in the background". Also not receiving message in onMessage.

I'm using Reac.js
"react": "^17.0.2",
"firebase": "9.6.7",

Any one can help?

@dwyfrequency
Copy link
Contributor

@Vijayakumarktm is this issue on Android Edge as well? If so, can you add the following details

  • Operating System version:
  • Browser version:

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?

@kanadaj
Copy link
Author

kanadaj commented Jun 29, 2023

@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)

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

No branches or pull requests

9 participants