Update README.md for iOS Web Push and VAPID credentials #197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add information about VAPID_SUBJECT for iOS webpush support.
cretueusebiu
merged commit 4276786
into
laravel-notification-channels:master
1 check passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Apple added web push support to iOS in 2023, there hasn't been a lot of details around what exactly is required.
Following the readme in this project, push notifications were working for Chromium browsers.
Apple follows a part of the spec that requires a VAPID subject to generate the push JWT. I found this specific information through a Java based library elsewhere on Github. web-push-libs/webpush-java#201 (comment)
Adding this information should make things a lot clearer for people trying to add native web push support to their web apps moving forward.