02-20-2012 08:56 AM
We have recently moved from eval push credentials to production push credentials. We have changed the push URL and password etc. in our client and server. The client is registering successfully, the server is getting successful responses when pushing, and a utilitiy we wrote that performs subscription checks correctly returns when the client is registered. The content provider portal shows our application as Active.
However, the messages never arrive on the client. It never gets past the "acceptAndOpen" blocking call in our client listen thread. This same code worked with the eval server.
One thing; I noticed in another thread that somebody had trouble as their Content Provider ID was not three digits and RIM assigned them a new one. Ours is two digits - so our push URL is https://cpXY.pushapi... etc... where XY is our CPID.
Can anyone here advise? Anyone else had this issue?
03-05-2012 04:56 AM
I replied to the push credentials email and the BB team replied within two days asking me to try again. I did so but it didn't work.
However, having spent a few days on something else, I came back to it on Friday to find that it worked, and has continued to work all weekend! No code change at our end, but hopefully this will continue...
03-06-2012 06:50 AM
Hi simon i am also getting the same problem here client side is registing fine but our server side i am not able to post data into blackberry server. i am getting error responses can u please tell me which one i wana use.
i am tried these are the urls at my server side.
can u please tell me which url i wana use.
03-06-2012 08:48 AM
This is the one to use....
Remember to replace "xxx" with your content provider ID in the first part of the URL.
"Request invalid" probably indicates the request is malformed in some way. Are you able to post the full XML push request (minus your private details/ids/passwords if needed), then maybe somebody can spot the issue?
03-06-2012 04:22 PM
I am having the same problem as you.
My service is up since april/2010, and it was working normally.... now it suddenly stoped working. I dont know when exactly.
I wonder if your email had some effect. Im gonna try to send it... hope they answer even if my service was released almost a year ago.