Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development


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.


Reply
Highlighted
Developer
Posts: 102
Registered: ‎07-15-2008
My Device: Not Specified

Carrier API restrictions with a RIM signed application.

I am getting ready to release my application on AT+T with RIM signing.  AT+T makes a big to-do about API restrictions and signing requirements for their Java apps on Java phones and seemed to imply it was required for Blackberry applications as well.  I have found this not to be the case, RIM signing gives me access to all the needed APIs without any carrier restrictions.  I'd like to release the application for my customers that run on other carriers (like Verizon/Sprint), but I wonder if they add additional restrictions or is RIM signing enough (like it is for AT+T).  Can someone share their experiences with other carriers?  Thanks!

Developer
Developer
Posts: 319
Registered: ‎07-20-2008
My Device: Not Specified

Re: Carrier API restrictions with a RIM signed application.

The only restriction I've run across is Verizon's lockdown of the Location APIs.

 

Developer
Posts: 120
Registered: ‎07-16-2008
My Device: 9000

Re: Carrier API restrictions with a RIM signed application.

Your BlackBerry Developer's signature will work with all carriers.  I have read in the APIs that AT&T also has some custom signature requirements around GPS but we have not run into this restriction.  Everything else is pretty much the same across carriers.  The main things that do vary across carriers are:

1.  How SMS is sent/received programatically

2.  The default application permissions

3.  APN information for making WAP connections 

Kurt Zettel | Chief Architect | Metova
www.metova.com
Developer
Developer
Posts: 319
Registered: ‎07-20-2008
My Device: Not Specified

Re: Carrier API restrictions with a RIM signed application.

Although the API docs do mention that AT&T requires separate signing, they never implemented it.  I've got 2 AT&T test devices and have full access to the location APIs.