I have been going through the process of creating and submitting a PlayBook app to App World and one of the new steps is code signing BlackBerry PlayBook apps. RIM has been kind enough to post up the two processes involved in code signing and I thought I would share them with you. Once again it seems needlessly complicated like regular Java BlackBerry app code signing but once you understand the steps it seems a little easier. Here they are:
There are two phases to the signing process: configuring your computer, and signing the application. You only need to configure your computer once. To configure your computer:
- Initialize communication with the RIM Signing Authority: The signing tool is designed to prevent tampering and eavesdropping on information it exchanges with the RIM Signing Authority.
- Register your CSJ registration file with the RIM Signing Authority: Once you have initialized the communication channel, you can register your CSJ file, which uniquely identifies you to the RIM Signing Authority.
- Ensure that you have a Developer Certificate: You can use the signing tool to create a developer certificate, or provide your own. If you create a Developer Certificate using the signing tools, ensure that the common name (company name) parameter matches what you enter in the Company field on the registration form. If you have an existing Developer Certificate you use to sign your Adobe® Flash® applications, ensure that the name you enter in the Company field on the registration form matches the common name (company name) of your existing certificate. You will not be able to sign your BlackBerry Tablet OS Application if these names do not match.
Once your development environment is configured, you’re ready to sign your application:
- Request a signature from the RIM Signing Authority: Use the signing tool to request that the RIM Signing Authority applies a signature to your application.
- Apply your signature: Use the signing tool to sign your application using your Developer Certificate.