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

Testing and Deployment

Unable to request signatures until this application has been registered

by Retired ‎02-17-2010 11:48 AM - edited ‎02-17-2010 04:21 PM (3,113 Views)


This article applies to the following:

  • BlackBerry® Java™ Development Environment (JDE)


In certain situations, when you attempt to sign your application using the SignatureTool application, you receive the following error:

Unable to request signatures until this application has been registered with all signing authorities required.


You are attempting to request code-signing signatures for your application but the SignatureTool is not registered with all the required signing authorities.

There are two types of RIM Code Signing framework signatures:

  • Required Signatures - This is specified by the .csl file associated with the .cod file. A required signature is necessary to load your application on the device.
  • Optional Signatures - This is specified by the .cso file associated with the .cod file. An optional signature indicates that the system may perform a runtime signature check on the application. If the application is not signed, it is not allowed to execute the intended method.

The SignatureTool prevents you from signing the application since it waits until all required signatures are in place. Required signatures are necessary for the application to load successfully on the device.


There are several different scenarios where the SignatureTool is not registered with the required code-signing servers.

Scenario 1 - Not Registered with Public Signing Authorities

There are three public-signing authorities (RBB, RRT, and RCR) that represent different sections of the controlled application programming interface (API). When you receive code-signing keys, you receive three .csi files representing the three code-signing servers. It is important to register with all three servers. To determine which signature keys have been successfully installed and/or missing, please review this article

Scenario 2 - Attempting to use a Controlled Signing Authority

There is an additional public-signing authority, the Certicom™ Crypto (RCC) signing authority, that controls access to Certicom cryptography functions on the device. Go to Certicom for more information on accessing the Certicom API’s on the device.

Scenario 3 - Attempting to use an Inaccessible Signing Authority

Research In Motion® maintains its own internal signing authorities for the protection of API’s that are not exposed or data that is not public. It is not possible to gain access to these signing authorities and any reference to Research In Motion internal methods or data should be removed from your application to allow the SignatureTool to sign your application.

Note: JDE 4.1 allows you to turn on code-signing warnings under Preferences. This determines the areas of your application that are attempting to use signatures from each signing authority.

Users Online
Currently online: 43 members 2,987 guests
Please welcome our newest community members: