-
Notifications
You must be signed in to change notification settings - Fork 30
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
Any plans to support Apples HTTP/2-based API? #16
Comments
Hi @wrtsprt. Currently there's nothing planned but I'll be more than happy to support you or anyone else contributing such improvement to the gem. Are you up for it? :) |
Hi @calonso, thanks for the offer. Will verify what's possible. Probably not an urgent issue since the binary API is still working. |
It would be very nice to add that feature (although not urgent right now as you pointed) and it would be even nicer to have a new committer on board!! ;) Hope you find it interesting and we see a pull request soon. Please let me know if you need any help on that. Regards |
This one might get deprecated, Apple can now use FCM for push notifications - if this topic is only related to push notifications then this only applies to older push use-cases. |
The ruby-push-notifications 's apns is not use at 2021.3.21 |
In case this is still an ongoing requirement, this should be possible by switching the client backend to httpx. |
I just realised that the use of the binary API is deprecated. Are there plans to support the HTTP/2 based API? Can we help?
The text was updated successfully, but these errors were encountered: