03-19-2007, 05:29 PM
Thumbs Must Hurt
Join Date: Jan 2006
Location: San Francisco, CA
Post Thanks: 0
Thanked 0 Times in 0 Posts
| | Pushes work with simulator but not the device
Please Login to Remove!
I'm working on an client-server application where the server listens for socket connections from blackberrys, retrieves some data and then sends the data out to MDS from where it is pushed to the device. All of this works fine if I'm running the device simulator and the MDS simulator.
However, if I try to do this with the actual device and the MDS simulator the device never seems to get the data. Even after waiting and continually re-logging in. By watching the logs I can see that the server and MDS are communicating and the MDS is pushing information out but after some debugging I found that the client continues to wait after the client begins listening for pushes.
I actually developed this app about a year ago and when I left it it worked fine. Now, at the request of my company, I'm back at it; however, I don't recall ever running into this problem. The client code has not changed at all. I had to change some server code but those changes are tangential to this issue. So, all I can think of is that there is some configuration step I'm leaving out.
I've ensured that the push port value is the same (100) on both the client and the server side. The MDS is running, as I mentioned, and I can browse to it using the blackberry browser on the device. I'm using pap push and a template file into which I substitute data that is needed for the push. Could it be that the format of the pap push envelope has changed and that the RIM network finds the envelope and its data unrecognizable? Yeah, I'm trying to think of everything here.
Any additional help is much appreciated.