Thanks for reporting the issue, @basvandenheuvel. I can't seem to replicate it.

• Were you able to reproduce it using quickstart?
• Have you noticed any significant logs from browser's DevTool?
• Could you share a working repro that we could run locally?

Hi @rommelpe , thanks for your reply.

1. I just tired the quickstart, also with the quickstart i do not get messages when the website has focus... i do get the messages in the background.

2. Haven't seen any logs.

3. I do not have anything for now...

Sorry for the confusion, @basvandenheuvel. It's an intended behavior. If the page is open and focused, you will not see a notification and as a result, you'll receive a callback in onMessage in the page.

If the page is in the background (i.e. not focused) the background message handler will be called and will show a notification.

See here:

Firebase notifications behave differently depending on the foreground/background state of the receiving app. If you want foregrounded apps to receive notification messages or data messages, you’ll need to write code to handle the onMessageReceived callback. For an explanation of the difference between notification and data messages, see Message types.

@rommelpe

I think i introduced the confusion.

It is indeed the onMessage callback that is not triggered when the website has focus. The same problem occurs when i connect our environment with the quickstart...

The process that should trigger in background does work...

I'm facing the same problem after upgrading from 7.6.2 to 7.8.0.
Background working but onMessage not receiving anything.

@basvandenheuvel did you find any solution?

@rommelpe i think this issue needs to be reopened.

Just checked 7.7.0 has the same problem.

@GoktuqCan not yet....

It looks like for me any version of 7.x.x is broken.

I doubt it is my firebase environment since the changelog is straightforward and we followed it. However, why else would their quickstart onMessage not work if i connect it to our environment...

@basvandenheuvel try npm i [email protected] and of course change importScripts versions in
firebase-messaging-sw.js(if you have) service worker with same version. This version working for me.

@GoktuqCan @rommelpe

Just tried again to make the quickstart work for me, no luck with eitehr 7.6.2 or 7.8.0.

I added the firebase config of my environment, i host the index.html and see a token being generated for me. I go to the firebase console page of messaging and send a test message.

Focus -> Nothing happens, i don't even see the console.log inside my onMessage
No focus -> i do get a windows notification, works as expected

@basvandenheuvel Are you just editing package.json or using the npm i [email protected] command?
If you just downgrading from package.json then package-lock.json may not be changed.

Thanks for getting back and continuing on working the issue, @basvandenheuvel @GoktuqCan. I was able to reproduce it using quickstart. It looks like the issue was introduced in v7.7.0.

@hsubox76 onMessage has stopped receiving responses from v7.7.0. Can you confirm if it's a bug on our SDK, intended behavior or might be related to our implementation?

There was a large refactor of the messaging codebase between 7.6.2 and 7.7.0. One of the changes may have impacted this. I'll try to dig into it. PR for my reference: #2484

Please make sure that your service worker is actually updated. You can force this by clearing site data in Chrome. Go to DevTools -> Application tab -> "Clear storage" from the menu on the left -> Clear site data.

onMessage works in my test app on 7.8.1 after doing what I described.

Thanks, @mmermerkaya. I was able to get rid of the issue after updating sw to latest version. Were you able to try it out on your end @basvandenheuvel @GoktuqCan?

Closing this issue. Should you have any other questions/clarifications, leave a comment and we're happy to look into it.

@rommelpe sorry but problem still remains.

@GoktuqCan Here's a sample response on my end after updating firebase-messaging-sw.js to v7.8.1. Were you able to reproduce it using quickstart?

You may want to check third party extension(s) on your browser that might be blocking the response. If nothing works after upgrading & clearing the browser's storage, the last resort would be reinstalling your browser.

@rommelpe i added a new user to chrome. New user is clean browser and it works for that one.
But what should users those already using application do now?
We cannot say everyone to clear browser storage. That doesn't work for current users that we have anyway.
You can reproduce using npm i [email protected](this one works) get token after that update to npm i [email protected](now working) get token. Try onMessage for both.
Note: Also updating firebase-messaging-sw.js too.

@GoktuqCan your users should get the updated service worker eventually. Browsers check for updates automatically after navigations and functional events such as push and sync.

@Feiyang1 Problem is not about receiving, it is about updating from previous version. Even if i hard reload page and clear cache, updating from 7.6.2 to 7.8.1 not working. If user starts to using application from 7.8.1 has no problem.

@GoktuqCan I believe your issue is that the installed sw which references 7.6.2 failed to update to the newer version that references 7.8.1.
I found that the timing by which browser updates sw is somewhat unpredictable, and it still confuses me.
I made a PR that manually updates sw when there is an update, so it will hopefully solve your problem. #2638

Once it is merged, can you try installing the canary build to verify if it fixes your issue? Thanks!

@Feiyang1 yes i can check.

@GoktuqCan The fix is in canary build. Can you please do npm i firebase@canary and see if your issue goes away?

@Feiyang1 canary version seems working now. In service worker canary version throw exception Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://www.gstatic.com/firebasejs/7.8.2-canary.261bbd54/firebase-app.js' failed to load.. So i used 7.8.2 instead.

Working versions are:
in package.json: "firebase": "^7.8.2-canary.261bbd54"
in firebase-messaging-sw.js:

importScripts('https://www.gstatic.com/firebasejs/7.8.2/firebase-app.js');
importScripts('https://www.gstatic.com/firebasejs/7.8.2/firebase-messaging.js');

Thanks for the help i guess fix will come with 7.8.3?

Awesome! thanks for confirming.
Yep, it will be in 7.8.3. the script error is expected, because we don't publish canary builds to CDN.