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

Android™ Development

New Member
Posts: 1
Registered: ‎06-25-2014
My Device: Z10
My Carrier: BB

Signing Issues



I'm trying to sign a new version of my ported apk application. I use the following command using the "old" command line tools (version 1.x):


batchbar-signer <bar-file> <dev-cert-path> <dev-cert-pass> <csk-pass>


I use a backed up author.p12 file and backed up passwords. As result I get the following error:


Signing with Developer Key.....
Error: Private key is not a DSA, RSA, or EC key


I used this command a few month ago on the same machine and it worked without issues. So what is the problem now?


Is it possible to switch to the new Blackberry ID Token signing system with my backed up csj, p12 files and the corresponding passwords?





BlackBerry Development Advisor
Posts: 15,784
Registered: ‎07-09-2008
My Device: BlackBerry PRIV
My Carrier: Bell

Re: Signing Issues

Try restoring your files as described here and sign without providing the path to your developer certificate (it should be picked up automatically).


Backup and Restore BlackBerry Code Signing Keys


If you haven't switched to using BlackBerry ID Tokens I recommend doing so.  But note that you will need to link your existing keys to your BlackBerry ID account.  Information on that can be found here:


Code Signing Keys Be Gone! Welcome BlackBerry ID

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker