-
Notifications
You must be signed in to change notification settings - Fork 904
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
Getting wrong fcm token in IOS #8697
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @pavelustenko, can you confirm whether in an iOS PWA:
Also, to help us isolate the issue, can you confirm that this works if you register the service worker at the default scope? |
Hi, @dlarocque , I will check a default scope configuration in few days. |
Hi, I got stuck while get token on safari. how can you get it? |
That's all very useful to know, thanks! You mentioned that the events aren't triggered on Safari iOS and macOS- is this on PWAs only? |
Hey @pavelustenko. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Operating System
IOS 18
Environment (if applicable)
Safari
Firebase SDK Version
11.1.0
Firebase SDK Product(s)
Messaging
Project Tooling
React Application. webpack
Detailed Problem Description
My PWA is deployed to /web-pwa context path on my server and it does not receive notification in IOS (Android works fine) presumably because of getting a wrong token when worker scope is dffer from default '/'
Steps and code to reproduce issue
App.js
firebase-messaging-sw.js
When I press 'initialize' button in PWA installed on real devices (Android phone and iPhone) I'm getting a FCM token successfully. But when I send test notifications from firebase console using tokens I got from apps, Android is showing notifications as expected, but no luck in IOS.
The text was updated successfully, but these errors were encountered: