search

pusher / push-notifications-web

Beams Browser notifications
MIT License
39 stars 19 forks source link

Lack of Web Push API Support for Safari Hindering Adoption of Pusher Beams in PWAs #146

Open jopar219 opened 11 months ago

jopar219 commented 11 months ago

Hi there! We hope you're doing well. We wanted to bring up a concern regarding Pusher Beams and its support for W3C's Push API on Safari.

As you may know, since February of this year, iOS has introduced support for W3C's Push API. However, it seems that Pusher Beams currently offers only beta support for Safari Push Notifications, a separate api specific to Apple that requires a .p12 certificate.

We were wondering if there are any plans to add support for W3C's Push API on newer Safari versions in the future. To provide a seamless push notification experience for our users, it's essential for us to have Push API support on Safari. With other alternatives already offering support for it, we are facing a tough decision regarding the adoption of Pusher Beams.

Implementing support for W3C's Push API on Safari could make Pusher Beams a more attractive choice for developers looking for a comprehensive push notification solution. It would also save us from dealing with the complexities of the legacy .p12 certificate requirement for Safari Push Notifications.

We really value your attention to this matter and would appreciate any updates or insights you can share with us. Addressing this would undoubtedly benefit the product. Thank you!

benw-pusher commented 11 months ago

As you have identified, Beams does not currently support web push notifications on Safari. While we do plan to add support for this to the product we don't currently have a timeframe for release. We'll update here as this changes.

RalphKemp commented 11 months ago

In the same position here at my company. Have tested out Beams and it works well for push, but will have to move over to a different service as we require support for this.

Developer-Mike commented 11 months ago

Same here. It's a shame, that this essential feature is not a priority. Considering migrating to another service...

HugoVonMemenchouser commented 10 months ago

We would appreciate support for this as well.

jopar219 commented 8 months ago

Are there any news regarding this feature? Is it difficult to implement? What would it require to fast track this?

v-stickykeys commented 8 months ago

Have moved away from pusher for same reason. Luckily with web-push this should be easy enough to roll your own. Also not clear pusher is doing anymore much more than that anyway on lower tiers. I'm setting up mine with a nice interface that you can plug a lambda service into (feel free to ping if you want to follow along/reuse).

rnystrom commented 7 months ago

I was really bummed to find this! We're big fans of using Pusher for websockets and we were hoping to just setup Beams and get pushes to iOS PWAs. We're going to look elsewhere for push unfortunately.

marcallkz commented 7 months ago

Same situation here. I have also asked about this earlier this year through a support ticket and the answer was the same. Unfortunately I'll have do switch to something else.

JoshuaSmeda commented 7 months ago

Disappointed to hear that this isn't a priority considering the large number of iOS and iPad devices in the wild. Unfortunately, it'll also force me to move to an alternative.

cl0ckwork commented 4 months ago

why do the official docs say pusher supports safari? What are these docs talking about then?

~I've managed to patch the push-notifications code to "make" it work on safari, and get all the way to the point where results are consistent with the docs (because the browser checks, which explicitly prevent safari usage, actually contradict the docs and are 5 years old...) and then get this error from the pusher backend service: presumably from another outdated user agent check.~

edit: seems like 2.0.0-beta.2i supposed to support safari in web - but i get the following error:

Unhandled Promise Rejection: Error: Unexpected status code 400: Token error, Push service endpoint not supported. The push subscription might be from an unsupported browser

I'd be very grateful if someone could please clarify what Pusher beams supports - beta supports web? maybe? Safari on Ios should work (functionality was added last year), but doesn't? What are the docs are talking about if Safari and Safari on IoS are not supported?

maegnes commented 4 months ago

Does anyone have a reliable provider alternative to pusher beams that supports Notifications via Web Push API on iOS?

DarthGigi commented 4 months ago

Does anyone have a reliable provider alternative to pusher beams that supports Notifications via Web Push API on iOS?

I switched to Firebase Cloud Messaging (FCM). Does everything you need and has iOS Web Push Notifications API support as well

ilkergzlkkr commented 4 months ago

Does anyone have a reliable provider alternative to pusher beams that supports Notifications via Web Push API on iOS?

I switched to native Web Push API and storing subscriptions on my database. Pretty easy to implement!