You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm facing a strange problem where push notifications are working perfectly in the sandbox environment but not in production. We have verified that the .p12 certificate is working and can use the same certificate to send push notifications from another server application.
I'm using the node plugin for eclipse and stepping through the code and it appears that the notifications aren't being sent at all. The reason for this seems to be because the queue, to which the push tasks have been assigned, is paused - ie has its _paused field set to true.
However, no error is being thrown and as a result my node server thinks the push notifications have been sent, yet the devices never receive them.
It also appears that the exports.gatewayOptions function is being called repeatedly (I checked this to make sure it was picking up the correct host, in terms of sandbox and production) as a result of listOnTimeout() in timers.js, Agent._reconnect() in live.js, and Agent.connect() in live.js. For what it's worth, it is picking up the correct production URL, but the fact that this method is called repeatedly - every five seconds or so - made me wonder if there were somehow connection problems.
Can you help?
Thanks very much in advance.
Bob
The text was updated successfully, but these errors were encountered:
You are totally true apnagent its not working.. i have the same problem..
I spend a lot of hours thinking that i was wrong with my production certificates or something like that but the problem was in apagent :(
I finally decided to migrate my code to https://github.com/argon/node-apn with same keys and same config putting the NODE_ENV=production. If you follow the instructions you'll achieve push in production environ
Hey guys & girls. I was having the same problem until I uncovered a simple thing. APNS Production and Staging device tokens are not identical. So, if you have a non-production build on your device (local testing) your device will have a 'Dev' device token. And if you send that device token with Production credentials, it will not be delivered. Simple. That was my issue which was my simple ignorance of APNS. Perhaps this helps others.
Hi,
I'm facing a strange problem where push notifications are working perfectly in the sandbox environment but not in production. We have verified that the .p12 certificate is working and can use the same certificate to send push notifications from another server application.
I'm using the node plugin for eclipse and stepping through the code and it appears that the notifications aren't being sent at all. The reason for this seems to be because the queue, to which the push tasks have been assigned, is paused - ie has its _paused field set to true.
However, no error is being thrown and as a result my node server thinks the push notifications have been sent, yet the devices never receive them.
It also appears that the exports.gatewayOptions function is being called repeatedly (I checked this to make sure it was picking up the correct host, in terms of sandbox and production) as a result of listOnTimeout() in timers.js, Agent._reconnect() in live.js, and Agent.connect() in live.js. For what it's worth, it is picking up the correct production URL, but the fact that this method is called repeatedly - every five seconds or so - made me wonder if there were somehow connection problems.
Can you help?
Thanks very much in advance.
Bob
The text was updated successfully, but these errors were encountered: