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
iOS pwa push notification issues #756
Comments
I think in your case, this might be because of the race conditions (which don't happen on Android). If you receive a lot of notifications at the same time, the service worker returns stale data for
I looked at the logs and they didn't fully explain what was going on. I noticed the bug that is fixed in #751 though. I didn't change the Android code though. So I am confused. I also wasn't able to reproduce the issue locally. Seems to only affect deposit notifications. [0] Created separate issue for this now: #763 |
Apple is pulling PWAs for their European users in iOS 17.4:
-- developer.apple.com, DMA and Apps in the EU, Developer Q&A Even though this only should affect EU users ("a small number of users"), I guess this makes their lack of priority regarding this more clear. So I believe we have come to a point where we seriously need to consider writing separate code just for Safari to use Safari Push Notifications:
-- developer.apple.com, Sending web push notifications in web apps and browsers I don't like this but I also want to get rid of this bug since it affects the ~20% of stackers that use iOS. I also have an iPhone now so I should be able to create an Apple developer account now (I think this is required) so I can implement this with no blockers. |
Seems the way to go unless we want to roll out an iOS app and I'd guess their special push notifications are less buggy. |
Figured we should just create persistent issue for this given they're numerous and hard to pin down:
The text was updated successfully, but these errors were encountered: