Open dvcrn opened 7 years ago
I debugged this a bit and noticed that in the case where the push notification doesn't work, it will:
Always in this pattern. On the other hand, on successful push the 2 last points don't occur.
Could it be that the library thinks it sent the push correctly only to receive the callback that the SSL socket got closed?
This might be similar to https://github.com/chvanikoff/apns4ex/issues/52
The way it works on Apple side is that any push is successful
as long as they receive it. Then they either deliver it to the device or send you error/feedback on a separate connection, which happens later. In any case SSL socket close is not good but I'm not sure how I can help in this case. I do not see this happening on my production setup.
Hello,
I noticed a problem in that push notifications strangely stop working after a few hours after server restart on Google Compute Engine. I was using Heroku before and didn't notice this problem but since migrating to google, it started popping up. (Not completely ruling out it didn't happen with Heroku as well)
I enabled full debug output to get an idea of what's going on but still can't figure out why the push notifications never make it to the device. After server restart it again works for a few hours.
This is probably a problem with Google. If you have any idea what could be causing this (since you implemented apns4ex), it would help us a lot.
My first thought was that a long-lasting connection got terminated so I adjusted
expiry
,timeout
andfeedback_interval
but no luck.Here is some debug output when sending a notification: