-
Notifications
You must be signed in to change notification settings - Fork 215
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
With gun-2.0.0-rc.1, apns reconnections are much more frequent than with gun-1.3.3 #245
Comments
Looks like
|
hi, this issue is more related with gun because we are built on top of 1.3.3 version and we don't plan to migrate it to a release candidate dependency. If you find any error with that gun version it would be good to share with gun folks, since it is still in a release candidate phase. |
This was referenced Mar 9, 2021
jainygaurav
pushed a commit
to jainygaurav/apns4erl
that referenced
this issue
Mar 19, 2021
For details, please refer to: inaka#242 inaka#245 ninenines/gun#261 ninenines/gun#263
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is in continuation with: #242.
Why reconnections are more in
gun-2.0.0-rc.1
compared togun-1.3.3
? Please help.When
apns4erl
was built withgun-1.3.3,
it was hitting issue #242. To resolve that issue, I buildapns4erl
withgun-2.0.0-rc.1
.Since then,
apns reconnections
are much more frequentFrom log timestamps, it looks like for every 2 hours.
However, I am able to send
push notifications
after reconnections and without any restart.I print these logs as errors when
apns4erl
sends{reconnecting, ServerPid}
or{connection_up, ServerPid}
messages to mygen_server
The text was updated successfully, but these errors were encountered: