-
Notifications
You must be signed in to change notification settings - Fork 677
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
Add support for APNS auth token (p8) #55
Comments
See #54 |
Isn't that a different thing? #54 is about using certificates over http/2 🤔 |
Well .. since the Pusher supports only the binary apple API and there are no plans to use the HTTP API, it means that it does not use the http (or http/2) API which is needed for sending pushes with token authentication. |
Makes sense. So it's related, but not the same. |
btw, I'm using Knuff but it also does not support token based auth :/ |
Do you guys know of any alternative that might have support for this? |
@andrejbroncek @BenchR267 @JanC in the meantime, you can use https://github.com/onmyway133/PushNotifications which supports APNS certificate, token and FCM authentication, works on both iOS and Android |
Pusheverapp free version does the job... Downloadable Mac App - https://github.com/cupnoodle/pusheverapp/releases/download/2.0t/PusheverTrial.app.zip |
Apple provides a way to send push notifications without the need of certificates by creating never expiring authentication keys (http://stackoverflow.com/questions/39943701/how-to-send-apns-push-messages-using-apns-auth-key-and-standard-cli-tools).
Unfortunately NWPusher does not support this kind of authentication yet.
The text was updated successfully, but these errors were encountered: