Signing your application
Before you can distribute your application for use on a BlackBerry device, you must sign your application. The signing tool included with the BlackBerry 10 SDK for Adobe AIR adds cryptographic hash values to your application package (.bar file) during the signing process. The hash files help verify the authorship of your application to users and the BlackBerry 10OS.
Beginning with the BlackBerry 10 SDK for Adobe AIR version 3.2.1, the BlackBerry ID token simplifies the signing configuration process by associating your signing keys with your BlackBerry ID, and elminating the need to request special signing keys.
If you want to test your application on a device without signing it, you can create and install a debug token on the device. For more information about debug tokens, see Using debug tokens.
To sign your application, you need to do two things.
Set up signing
To set up signing, use the BlackBerry deployment setup wizard in Adobe Flash Builder or FDT. This wizard runs when you create an Adobe ActionScript Mobile Project and guides you through the configuration process to sign your applications or test them on a BlackBerry device.
For more information on using the deployment setup wizard, see Configure your development environment using Flash Builder or Configure your development environment using FDT.
If necessary, you can manually configure your environment for application signing by using the command line tools. For more information on using the command line tool, see Configure your application using the command line.
Sign your application
Sign your application by requesting a .bar file signature from the BlackBerry Signing Authority.
You must increment the version number of your application each time you sign it. For more information on updating the version number, see Update application version number
After you sign your application, you can publish it to the BlackBerry World storefront.