Troubleshooting app signing errors
When you sign your application, you may periodically experience problems.
The following table describes the application signing errors you might encounter.
|Attempt to rename value1 to value2 failed||
During the signing process, the signing tool makes a copy of the input BAR file (.bar file). After the tool signs the copy of the BAR file successfully, the copy is renamed to the original input file name and the original file is deleted. This error indicates that one of these rename operations failed.
|Make sure that you have permissions to modify files in the folder where your BAR file is stored.|
|Code signing request failed because Application-Development-Mode in Manifest is present and is not set to false||This message appears when you try to sign a BAR file that was packaged in Development mode||Repackage the BAR file. If you use blackberry-nativepackager, or another command line tool, do not include the debug option in your command line.|
|Code signing request failed because Common Name in developer certificate is not [value]||The Common Name (CN) property in your Developer Certificate does not match the value you provided in the Company field when you requested permission to sign applications by using the RIM Signing Authority.||
Create a self-signed Developer Certificate using the blackberry-keytool tool, that has a CN property that matches the name you provided when you requested permission to sign applications.
Reapply for permission to sign applications with the RIM Signing Authority located here . On the web form, in the Company field, provide the name that appears in your Developer Certificate.
|Code signing request failed because this file has been previously signed||You can sign an application only once per version number.||
|Code signing request failed because Package-Author in Manifest is not set to [value]||The publisher element in your application descriptor file does not match the value you provided in the Company field when you requested permission to sign applications by using the RIM Signing Authority.||
Change the value of the publisher element in your application descriptor file file.
Reapply for permission to sign applications with the RIM Signing Authority at here . On the web form, in the Company field, provide the name that appears in your publisher element.
|Code signing request failed because value of Package-Name in Manifest is not allowed||Your application has a name that is restricted.||
|-cskpass and -csjpin must be specified if -register is specified||
This message appears when you try to run the blackberry-signer tool with the register option, but you did not include both the cskpass and csjpin options.
The blackberry-signer tool tries to encrypt communication between your computer and the RIM Signing Authority. The tool stores the encryption keys in an encrypted file that is designed to be unlocked by using the password you provide in the cskpass option.
The CSJ Pin is a 6- to 10-digit number you selected when you requested permission to sign applications. The number is designed to verify that the CSJ registration file is used only by the person who requested it.
|Add the cskpass and csjpin options to your command line. Make sure you provide appropriate values for each option.|
|cskpass required||You requested a signature from the RIM Signing Authority, but did not include the cskpass option. To contact the RIM Signing Authority, the blackberry-signer tool must decrypt the barsigner.csk file using the password you provide using the cskpass option.||Include the cskpass parameter and the password in your command line.|
|Developer certificate and private key not found in keystore or store password not supplied||You attempted to sign an application using the blackberry-signer tool, but you did not provide a value for the storepass option, or your Developer Certificate has no private key named "author".||
Verify that your command line includes the storepass option and specifies the correct password.
Recreate your Developer Certificate. You can use the blackberry-keytool tool. Make sure that you provide the literal value "author" (not your name) for the alias option.
|Incomplete certificate chain||The Developer Certificate that you provided to the blackberry-signer tool was issued by a Certificate Authority. However, the series of signatures (from a root authority to your certificate) that establish the authenticity of your certificate was not found in your keystore along with your Certificate.||Add the certificate chain to the keystore.|
|Key associated with [value] not a private key||The blackberry-signer tool found a application signing key using the keyname parameter you specified on the command line. However, the key found is inappropriate for application signing.||
|Keystore load: store password incorrect||The value you specified for the storepass option is incorrect. The blackberry-signer tool cannot decrypt the keystore for your Developer Certificate.||Provide the correct password for your keystore.|
|keytool error: java.io.FileNotFoundException: certificate.p12 <Access is denied>||You tried to use the blackberry-keytool tool to create a self-signed Developer Certificate. The tool does not have permission to write to the location you provided for the output_file.p12 parameter.||
Acquire read-write permissions for the folder to which you want to write the P12 file.
Choose another location for your P12 file.
Run blackberry-keytool with superuser permissions.
|keytool error: java.lang.Exception: Key pair not generated, alias <author> already exists||You tried to use the blackberry-keytool tool to create a self-signed Developer Certificate. The file name you provided for the output_file.p12 parameter already exists.||
Change the file name so that blackberry-keytool creates the output file using a different name or location.
Delete your existing P12 file. Then run blackberry-keytool again.
|Missing parameter for [option_name] option||You specified a command line option, option_name, that takes a parameter. However, you did not supply a value for the parameter.||Provide a value for the parameter.|
|No BAR file or CSJ file specified||
This error appears when you try to use the blackberry-signer tool to sign or verify a BAR file, but no BAR file was specified on the command line.
This error can also appear when you try to use the blackberry-signer tool to register with the RIM Signing Authority, but no CSJ file was specified on the command line.
|Specify the appropriate file.|
|No key name specified||
You cannot sign your BAR file because you did not specify a signing key.
The final parameter of the blackberry-signer tool specifies the key with which to sign your BAR file. Your BAR file must be signed twice: first by the RIM Signing Authority, then by your Developer Certificate.
To request a signature from the RIM Signing Authority, type RDK at the end of your command line.
To sign your BAR file using your Developer Certificate, type author at the end of your command line.
|No manifest||The BAR file is corrupt.||Repackage your project using the blackberry-nativepackager tool.|
|Only one of -setup, -register, or -verify can be specified||You cannot execute any of the following functions concurrently: setup, register, and verify. They are mutually exclusive operations.||Perform these functions separately.|
|Server is not responding||
The signing tool cannot contact the RIM Signing Authority.
A problem with the network connection prevents the blackberry-signer tool from contacting the RIM Signing Authority. The signing tool cannot sign your BAR file until it contacts RIM Signing Authority.
|Check your computer's network connection.|
|Signature filename must consist of the following characters: A-Z, 0-9, _ or -||The value for the keyname option on the blackberry-signer command line contains unexpected characters.||The keyname must be RDK or author.|
|Unable to open BAR file||The blackberry-signer tool cannot read the BAR file you specified on the command line. You may not have permission to access this file, or the file may be missing or corrupt.||Verify that you have permission to access the file and that it exists at the location you provided on the command line. If the file exists and you have access to it, then try repackaging your project using the blackberry-nativepackager tool.|