Aple push Notifications not working on production/final version

#1

During the development, all the tests went well.
Although, with the final version (the one available on the iTunes), the notifications don’t work.

When I run my PHP I keep getting an error saying “SSL: Broken pipe” in this line, right after the first 10 or 20 messages.:
[php]$result = fwrite($fp, $msg, strlen($msg));[/php]
But none of the devices are receiving the PUSH.

My AppID is configured with both the production and the development certificate, and the devices are all registering their device tokens on our database.

I thought it might have something to do with the use of latin characters like “ç” and “ã” in the message, but I tried with a different simple 38-character-long message and the result is always the same.

Anyone can share some information on this behavior? [import]uid: 123238 topic_id: 35962 reply_id: 335962[/import]

#2

Hey Paulo, were you able to sort this out?

The Push Notification I implemented used to work, but it stopped working. When I run the PHP script, I get “Push notification successfully delivered” message, but the device isn’t getting any. On device settings, under the Notifications, my app is listed and everything is turned on. The app has not been released yet, so I’m testing AdHoc build with production certificate. This used to work… and the code, certificate, ck.pem files have not changed… What could have gone wrong? Any idea?

Naomi

Edit: I was reading up on migrating to a cloud service, and I read something about needing my own SSL if I were to use my own custom domain. So I’m wondering if the “SSL: Broken pipe” message you get has something to do with SSL not properly in place with your production server. Or do you use the same server for both development and production/live versions? [import]uid: 67217 topic_id: 35962 reply_id: 144430[/import]

#3

Are you sure you’re using the production servers and not the sandbox servers? My code from the push blog post:

ssl://gateway.push.apple.com:2195

and not

ssl://sandbox.gateway.push.apple.com:2195

or something like that?
[import]uid: 199310 topic_id: 35962 reply_id: 144490[/import]

#4

@Rob, yes I’m using the production servers.

@Naomi, still bugged. But that SSL question makes some sense.
Should we access our PHP (the one that connects to the APS) over an HTTPS address?
I don not have that right now?
Can you test it Naomi?
[import]uid: 123238 topic_id: 35962 reply_id: 144505[/import]

#5

@Paulo, I’ve never used HTTPS address for the Push Notifications – I mean, I don’t use HTTPS for the PHP URL. And it used to work perfectly fine. In addition, even though, for whatever reason, none of the notifications make it to any of the devices I send to anymore, I certainly do not get the “SSL: Broken pipe” message. What I get is “Push notification successfully delivered” message. So I don’t think not using HTTPS address is causing your issue.

I just don’t know if non-SSL enabled webserver can send a request like ‘ssl://gateway.push.apple.com:2195’

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144545[/import]

#6

Hey, @Paulo, just in case it helps, here’s another thread about Apple’s push notification not working quite right:

http://developer.coronalabs.com/forum/2012/12/21/push-notification-dialog-not-appearing-anymore-unable-get-device-token#comment-144582

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144595[/import]

#7

That thread makes me feel like it’s an Apple problem. [import]uid: 199310 topic_id: 35962 reply_id: 144603[/import]

#8

Hey Paulo, were you able to sort this out?

The Push Notification I implemented used to work, but it stopped working. When I run the PHP script, I get “Push notification successfully delivered” message, but the device isn’t getting any. On device settings, under the Notifications, my app is listed and everything is turned on. The app has not been released yet, so I’m testing AdHoc build with production certificate. This used to work… and the code, certificate, ck.pem files have not changed… What could have gone wrong? Any idea?

Naomi

Edit: I was reading up on migrating to a cloud service, and I read something about needing my own SSL if I were to use my own custom domain. So I’m wondering if the “SSL: Broken pipe” message you get has something to do with SSL not properly in place with your production server. Or do you use the same server for both development and production/live versions? [import]uid: 67217 topic_id: 35962 reply_id: 144430[/import]

#9

Are you sure you’re using the production servers and not the sandbox servers? My code from the push blog post:

ssl://gateway.push.apple.com:2195

and not

ssl://sandbox.gateway.push.apple.com:2195

or something like that?
[import]uid: 199310 topic_id: 35962 reply_id: 144490[/import]

#10

@Rob, yes I’m using the production servers.

@Naomi, still bugged. But that SSL question makes some sense.
Should we access our PHP (the one that connects to the APS) over an HTTPS address?
I don not have that right now?
Can you test it Naomi?
[import]uid: 123238 topic_id: 35962 reply_id: 144505[/import]

#11

@Paulo, I’ve never used HTTPS address for the Push Notifications – I mean, I don’t use HTTPS for the PHP URL. And it used to work perfectly fine. In addition, even though, for whatever reason, none of the notifications make it to any of the devices I send to anymore, I certainly do not get the “SSL: Broken pipe” message. What I get is “Push notification successfully delivered” message. So I don’t think not using HTTPS address is causing your issue.

I just don’t know if non-SSL enabled webserver can send a request like ‘ssl://gateway.push.apple.com:2195’

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144545[/import]

#12

Hey, @Paulo, just in case it helps, here’s another thread about Apple’s push notification not working quite right:

http://developer.coronalabs.com/forum/2012/12/21/push-notification-dialog-not-appearing-anymore-unable-get-device-token#comment-144582

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144595[/import]

#13

That thread makes me feel like it’s an Apple problem. [import]uid: 199310 topic_id: 35962 reply_id: 144603[/import]

#14

Hey Paulo, were you able to sort this out?

The Push Notification I implemented used to work, but it stopped working. When I run the PHP script, I get “Push notification successfully delivered” message, but the device isn’t getting any. On device settings, under the Notifications, my app is listed and everything is turned on. The app has not been released yet, so I’m testing AdHoc build with production certificate. This used to work… and the code, certificate, ck.pem files have not changed… What could have gone wrong? Any idea?

Naomi

Edit: I was reading up on migrating to a cloud service, and I read something about needing my own SSL if I were to use my own custom domain. So I’m wondering if the “SSL: Broken pipe” message you get has something to do with SSL not properly in place with your production server. Or do you use the same server for both development and production/live versions? [import]uid: 67217 topic_id: 35962 reply_id: 144430[/import]

#15

Are you sure you’re using the production servers and not the sandbox servers? My code from the push blog post:

ssl://gateway.push.apple.com:2195

and not

ssl://sandbox.gateway.push.apple.com:2195

or something like that?
[import]uid: 199310 topic_id: 35962 reply_id: 144490[/import]

#16

@Rob, yes I’m using the production servers.

@Naomi, still bugged. But that SSL question makes some sense.
Should we access our PHP (the one that connects to the APS) over an HTTPS address?
I don not have that right now?
Can you test it Naomi?
[import]uid: 123238 topic_id: 35962 reply_id: 144505[/import]

#17

@Paulo, I’ve never used HTTPS address for the Push Notifications – I mean, I don’t use HTTPS for the PHP URL. And it used to work perfectly fine. In addition, even though, for whatever reason, none of the notifications make it to any of the devices I send to anymore, I certainly do not get the “SSL: Broken pipe” message. What I get is “Push notification successfully delivered” message. So I don’t think not using HTTPS address is causing your issue.

I just don’t know if non-SSL enabled webserver can send a request like ‘ssl://gateway.push.apple.com:2195’

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144545[/import]

#18

Hey, @Paulo, just in case it helps, here’s another thread about Apple’s push notification not working quite right:

http://developer.coronalabs.com/forum/2012/12/21/push-notification-dialog-not-appearing-anymore-unable-get-device-token#comment-144582

Naomi [import]uid: 67217 topic_id: 35962 reply_id: 144595[/import]

#19

That thread makes me feel like it’s an Apple problem. [import]uid: 199310 topic_id: 35962 reply_id: 144603[/import]

#20

Hey Paulo, were you able to sort this out?

The Push Notification I implemented used to work, but it stopped working. When I run the PHP script, I get “Push notification successfully delivered” message, but the device isn’t getting any. On device settings, under the Notifications, my app is listed and everything is turned on. The app has not been released yet, so I’m testing AdHoc build with production certificate. This used to work… and the code, certificate, ck.pem files have not changed… What could have gone wrong? Any idea?

Naomi

Edit: I was reading up on migrating to a cloud service, and I read something about needing my own SSL if I were to use my own custom domain. So I’m wondering if the “SSL: Broken pipe” message you get has something to do with SSL not properly in place with your production server. Or do you use the same server for both development and production/live versions? [import]uid: 67217 topic_id: 35962 reply_id: 144430[/import]