To test and debug your code before you receive the code signatures, you can use the BlackBerry® Smartphone Simulator. You
must sign the application before you install it on BlackBerry devices. You do not send your actual code to RIM. You can use the
BlackBerry® Signature Tool to send a SHA-1 hash of your code file so that the signing authority system can generate the necessary
signature.
For more information about registering and obtaining code signatures, see the BlackBerry Signing Authority ToolVersion 1.0 -
Password Based Administrator Guide. For more information about registering and using classes, visit
www.blackberry.com/
developers/index.shtml
.
BlackBerry APIs with controlled access
You can run applications that use controlled APIs in the BlackBerry® Smartphone Simulator without code signatures; however,
you must obtain code signatures from Research In Motion before you can install these applications on BlackBerry devices.
You can use the following categories of RIM controlled APIs:
•
Runtime APIs
•
BlackBerry® Application APIs
•
BlackBerry Cryptographic API
If you use any of the following BlackBerry API packages, your application requires code signatures before you can install it on a
BlackBerry device:
•
net.rim.blackberry.api.browser
•
net.rim.blackberry.api.invoke
•
net.rim.blackberry.api.mail
•
net.rim.blackberry.api.mail.event
•
net.rim.blackberry.api.menuitem
•
net.rim.blackberry.api.options
•
net.rim.blackberry.api.pdap
•
net.rim.blackberry.api.phone
•
net.rim.blackberry.api.phone.phonelogs
•
net.rim.device.api.browser.field
•
net.rim.device.api.browser.plugin
•
net.rim.device.api.crypto.*
•
net.rim.device.api.io.http
•
net.rim.device.api.notification
•
net.rim.device.api.servicebook
•
net.rim.device.api.synchronization
•
net.rim.device.api.system
For more information about RIM controlled APIs, see the BlackBerry API reference.
Fundamentals Guide
BlackBerry APIs with controlled access
37
