firebase-js-sdk
firebase-js-sdk copied to clipboard
FR: Safari Push Notification Support (via APN)
Any plans on supporting the Safari Push Notifications (implement APN handling and conversion to FCM keys)?
https://developer.apple.com/notifications/safari-push-notifications/
+1
+1
+1
+1
+1
+1
+1
+1
+1
This is really needed, still doesn't work in Safari 13
+1
can we use any third party notification which interact with FCM?
Just wondering if there are any updates on this issue as it seems to be completely silent except from users of Firebase.
Would love an update on this, this is sorely needed
+1
+1
Same here, it's a big turn down for us, it represents 27% of the Market Share on mobile, and 3% on desktop.
Ignoring Safari on mobile is definitely not an option in our PWA.
@andreasanta You mention Safari on iOS but even Apple's own APN push notifications only work on macOS currently. There is no support for push messages in Safari on iOS. No amount of money, development will change that unless Apple deems it worth the time to implement.
That said: I'd love Safari on macOS support so consider me /subbed
@rejhgadellaa So unfortunately true! I thought APN would work on Safari iOS. Apparently, Apple is still determined to restrict core functionality to Apps, so they can cash in a while longer on the App Store purchases. You're right, nothing can change that unless they open the functionality to PWAs.
YUP, lack of iOS support truly sucks. But I'm pretty sure that when it is finally introduced by Apple - it will be implemented in FCM, won't it?
+1
I'm sure native iOS support is coming. Meantime, macOS support would be nice.
+1
+1
I'm at a bit of a loss here. I did what I thought was my due diligence to recommend FCM to a client. Only after finding the messaging/unsupported-browser error in console did I search Stack and realize that macOS Safari, despite Google having an implementation green light, is not supported by FCM.
Checking the WebKit feature roadmap there are no indications that Apple will ever support the Push API. This is 100% in Google's court to implement. There's no point in playing Push API chicken with Apple anymore.
We are already fully prepared to tool up for APN certs for our mobile app, I see no reason why we, as Firebase customers, should be expected to ignore macOS Safari for this feature. I have no idea if this is a political move or not, but either way I don't think we should be left out in the cold here.
@Feiyang1 @mmermerkaya
Is there any progress on this? Increasingly important with Flutter web, and no word for almost two years...
Hey folks, Thanks for expressing great interest in having FM supporting MacOS Safari sends. Apologies for the negligence on this long standing FR. I have brought this up to the team and want to share some updates:
- FM team has been committing to an internal infrastructure improvement program. Limited capacity is currently dedicated to new features.
- This FR is in the front queue of the next to be implemented.
- We are pushing to reprioritize this feature to fit into the infra program.
I'll keep the thread posted on any updates. Cheers.
At last! Thank you and, well, let's wait some more ;)
Good to see that we are finally making progress 🎉
Happy to hear and thanks for the update and transparency
OK, given the push service is not available yet, is there anyway i can only use the send / subscribe feature while user's page is open? I only want to use FCM as a service for the server to send connected client data update event. The missing of safari support becomes the major block to me
@neekey I assume you are targeting Mac OS Safari. Unfortunately, until this feature is released, you will need to find another way to push data payloads to your Mac OS Safari clients. But you probably know you could already do it to other browsers with the FM SDK with the caveat that you can't silent push.