Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
07-11-2010 06:36 AM
I was getting rc=10001 while registering with RIM server. Searching in forums I found that this issue happens when the PIN number is not included in the request.
But after doing a lot of head banging, I changed the eval url of https to http. The suddenly I started receiving param as response and I was able to register and receive push messages. So if anybody is having problems then try to use http instead of https. I hope my way is correct. Is using https will effect my final production system?
08-06-2010 11:18 AM
Changing to HTTP worked for me also, after getting rc=10001 when using HTTPS.
Note that in RIM's client sample app from the Push SDK, the com.rim.samples.device.push.PushConfig class has a bpasUrl property with a default value of http://pushapi.eval.blackberry.com.
For portal access, and for content provider pushes, I think HTTPS should be used.
08-30-2010 03:35 PM
For BlackBerry Push Service connection URL you need to use http on the device side and https on the server side.