02-05-2012 05:47 PM
Oh Snap! Build request failed with message: [ERROR] Signing failed Failed to decrypt keystore, invalid password
I tried the passwords that I had used in this command but with no luck;
blackberry-signer -register -csjpin <pass1> -storepass <pass2> .csj .csj
02-10-2012 10:10 PM
I've also got this problem, but using the WebWorks SDK via the Mac OS X Terminal. I can use bbwp to create a .bar file. But if I try to use bbwp to simultaneously sign the .bar, it fails with the message "Failed to decrypt keystore, invalid password".
I *just* installed everything to start code signing, so I know I'm inputting the exact same keystore password (I can still see the install command in my terminal). Any idea why I'm getting this error?
02-13-2012 12:34 AM
In my case, I think something happened when I first registered the keys, because I initially had an error but later got the servers to register my keys. Unfortunately, I changed my storekey halfway, thinking that the first attempt had failed and that I should choose something more secure (a randomly generated password instead).
So I deleted the old files (located in Library/Research in Motion on my mac), requested new keys, and registered them successfully. I have been able to sign apps with these keys.
Basically, start over with fresh keys. I could do this because I haven't yet submitted the app. Beware that if you already have an app in the App Zone, and you change your signing keys, you will no longer be able to update the same app (afaik).
05-10-2012 11:54 AM
No resolution to this then? I'm getting the same error when using the Ripple Chrome extension. I know the password is correct because I just used the password to sign an app through Android Runtime online, so it really can't be wrong.
02-06-2013 09:24 AM
I tried to signed my HTML5 apps using ripple ,command promnt and also the graphical tool of blackberry,still getting the same error "Failed to decrypt keystore".I have tried with 10-12 different keys ,Please help me out .
Thanks in advance
02-12-2013 01:21 PM
That means your password is incorrect. If this is a first time setup and you are trying to create all new keys with a new password, make sure you remove all files described here: