getToken hangs

[marcusx2]

Operating System

macOS 13.6.3

Browser Version

Safari 17.2

Firebase SDK Version

10.7.0

Firebase SDK Product:

Messaging

Describe your project's tooling

index.html with source tag. Just javascript.

Describe the problem

getToken suddenly stopped working and now it just hangs. The promise never fulfills or rejects. Seems like I'm not the first to report this issue either, with a quick google search it was reported before.

Don't know if it's related or not, but the problem happened after I started playing with the quick-start, when sending a test message at some point I deleted all the FCM registration tokens using the firebase console

,

and now I can't get a new one.

Steps and code to reproduce issue

I have no idea. I didn't do anything special. I was struggling to get the notification but I was getting the token. Now I can't even get the token ;_;. I also tried creating new vapid keys, to no avail. I can't use the api at all at this point.

[marcusx2]

I managed to "fix" the problem by uploading the build to netlify. With the build hosted there I can get the token, but I can no longer test locally with ws --https. Still, no notifications, but at least the onMessage works. So the message is being delivered, but I can't for the life of me get notifications to work. Not sure if the getToken hanging is an issue with the local server or something. Maybe some state or whatever can get corrupted and then getToken never works again, might be worth looking into, but I have no other clues.

[looptheloop88]

Hi @marcusx2, I wasn't able to replicate this issue. The FCM token is getting generated and refreshed successfully when I open the app using the latest version of Google Chrome and Safari 17.2. Also, both browsers are able to receive the test messages I sent via notifications composer console.

I am not really sure if your local server set up is the one causing the issue. But by just using the quickstart project, you may run the npm run dev command and your app will be hosted on localhost. You just need to update the service worker script and use these lines of codes, instead of these ones.

To isolate the issue, you may try my suggestion above and see if the issue persists.

[marcusx2]

You just need to update the service worker script and use these lines of codes, instead of these ones.

Yes like I said, I am able to trigger the onMessage, with the app hosted on netlify. Locally it doesn't work anymore, and never mind notifications. I only managed to get them 2 or 3 times and never again. I guess this can be closed, I have nothing else to offer.