-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Parse-maintained node-apn #6057
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
Comments
Parse does maintain its own fork of node-apn for some weeks now. Exactly for this reason: We want to be able to change code without relying on an inactive node-apn repository. As far as I can see this issue could be fixed if we merge this into our fork: node-apn/node-apn#643 Correct? |
If everyone agrees on this I can apply the changes to our fork tomorrow. |
@Vortec4800 In case you have some time to work on it you could also create the PR to our fork: https://github.com/parse-community/node-apn |
That is my (admittedly limited) understanding as well. I might be able to do it later today, if so I'll put together a PR. |
I found some time this morning and created a PR with the required changes: parse-community/node-apn#7 |
Cool thanks for this, will be good to get this merged and updated when it's ready. |
closed via parse-community/node-apn#7 |
Is Parse maintaining their own fork of node-apn now? I'm getting a ton of errors when sending push messages about HTTP2 GOAWAY handling that seem to be related to this issue/PR: node-apn/node-apn#640
That's from quite a while ago now and it seems like it's not going to be merged in, and even if it is I don't know if it would get merged in the new Parse fork.
The text was updated successfully, but these errors were encountered: