Requesting a signing account
To start developing applications using the BlackBerry 10 Native SDK, you'll need to request signing keys. The signing keys are free, and you'll need to request them from Research In Motion.
The signing application included with the Native SDK adds cryptographic hash values to your application package (BAR file) during the signing process. The hash values help verify the authorship of your application to other users and the BlackBerry 10 OS. The code signing keys also include a key for generating a debug token, which is required to run your application on a device. Debug tokens are only necessary to test on devices, not for the simulator.
The following steps describe the application signing process. There are two phases in the signing process. In the first phase, you configure your computer to sign applications. You should need to configure your computer only once. To configure your computer:
- Request permission to sign BlackBerry 10 OS applications by completing the web form here. After your application is accepted, you receive two CSJ registration files by email. a RIM® Development Key (RDK) file to sign the application and a debug token (PBDT) file to generate debug tokens. Each file arrives in a separate email with information about the purpose of the file attached.
- Complete the BlackBerry 10 OS deployment setup wizard. This wizard runs when you create a new project for your application, and guides you through the configuration process to sign your applications or test them on a device. If necessary, you can manually configure your environment for application signing.
- Sign your application by requesting a .bar file signature from the RIM Signing Authority. You must increment the version number of your application each time you sign it.
The CSJ registration files are used to configure your computer to create debug tokens. When you create a debug token, you specify a PIN for each device on which the token can be used. The debug tokens are valid for 30 days. When a debug token expires, the device no longer allows unsigned apps that rely on that token to run. When the token expires, you can generate a new one using the same CSJ keys.
Ensure that you save these registration files on your computer and back them up. You will need them when you configure your environment.