05-13-2012 08:00 AM
I have a issue for creating a debug token to install on my playbook.
* I have installed the SDK for a long time ( before the playbook was here ), so when I first installed it, there was no debug token / PBDT files
* Then I received my PBDT file by mail, but didn't used it as I was more accustomed to using the simulator.
* I since published a Android application.
I have some barsigners files in the "C:\Users\MY_NAME\AppData\Local\Research In Motion" folder. I think they were created when I published the Android application.
So now when I try to create a debug token with this command :
blackberry-debugtokenrequest -storepass XXX -devicepin XXX c:\temp\debugtoken.bar
And I have this error :
Error: The signature on the code signing request didn't verify. The likely cause of this problem is entering an incorrect CSK password.
My store pass is correct ( I have another error if I intentionally use an incorrect password ).
Can it be my PBDT.csk file that is badly registered ?
How can I change that ?
Thanks for any help,
I need it because I now have a bug that does not occur in ripple or on the tablet simulator.
Emmanuel / Alocaly
Solved! Go to Solution.
05-15-2012 04:32 PM
The only cause I know of for that error is using an incorrect password. Have you created multiple .p12 files? Maybe you have created more than one of those with different passwords. What .p12 files do you see in "C:\Users\MY_NAME\AppData\Local\Research In Motion"?
05-17-2012 06:11 AM
Hi Mark, and thank your answer.
Actually, I don't think it is a password issue :
if i intentionally set a wrong password, I have immediatetely this error :
"Error : Failed to decrypt keystore, invalid password"
( So i guess, it don't even try to connect to the Blackberry servers )
If I enter the correct password, I have to wait one or two seconds before I have the error :
"Error : The signature onthe code signing request didn't verify. The likely cause of this problem is entering an incorrect CSK password"
( So I guess the error occured after some communications with BlackBerry servers ).
As for my .P12 files in "C:\Users\MY_NAME\AppData\Local\Research In Motion" :
I have a sigtool.p12 and a author.p12 files.
But they both are really the same file that I renamed ( as said in the docs ).
Actually, I've just search on my whole hard disk, and I don't have other .p12 files than these ones.
I also just tried again without the sigtool.p12, but I had the same result.
Should I recreate some files ?
If I recreates the signings files, will I still be able to sign my shipped applications ?
05-17-2012 09:41 AM
The first error is a local password failure, the second is a password failure after connecting to our servers.
It looks like you may have used 2 different passwords when creating your keys (one for the .p12 and another for the .csj files). This is possible if you installed using the command line or used early versions of the BlackBerry Tablet OS SDK for Adobe AIR (newer SDKs for the same password).
Give your existing .p12 files a new extension and create a new p12 with the password used for the CSJ files. If you need instructions for that let me know which SDK you are using. You can safely create a new p12 file and still sign your applications. Do NOT remove the RIM Code Signing Keys (sigtool files) created by installing the CSJ files.
05-18-2012 07:48 AM
And thanks again for your help.
You are certainly right about the password, I created them with the first released SDK ( so before the playbook was available ).
And I'm a little confused by all the different password.
I have a keygen password ( the one for the .p12 file ), and one for the CSK ( I'm not really sure where it came from ), and also a PIN number I gave at the start.
And they all are different.
So you say I should recreate a new .p12 file ( does it mean I will also recreate the barsigner files ? )
I'm currently using the latest tablet SDK : 184.108.40.206
Thanks for your help,
Emmanuel / Alocaly
05-18-2012 03:36 PM
Ok, the different password for the Developer Certificate (p12) and RIM Code Signing key would cause issues here. Rename your author.p12 to something else and create a new p12 with the same password as your RIM Code Signing keys. Don't delete the barsigner files or you won't be able to sign upgrades of your applications. This command will allow you to create a new p12 file.
blackberry-keytool -genkeypair -storepass <create_a_password> -dname "cn=<company_name>"
05-19-2012 09:15 PM
And thanks again for your answer !
Actually, it worked.
So I could :
* Regenerate my p12 file with the same password as the csk one
* create and install the debug token
* still sign upgrades of my applications
The only issue I had was that while installing my (unsigned) application, I had this error :
result::failure 881 application author does not match debug token author
After investigating, reading the forums, and unzipping the token and the generated bar files, I finally added a blackberry-tablet.xml file next to my config.xml file.
This file is a copy of the one I found in the SDK, but with the author and authorId field added.
With this modification, everything looks fine.
I just wanted to check that was I have done is safe
Thanks for your support !
Emmanuel / Alocaly
05-28-2012 04:24 PM
Glad to hear you are back up and running.
Everything you did looks fine to me.
07-03-2012 04:25 PM
Package-Author and Package-Author-ID can be read in the MANIFEST.MF file located in the meta-inf directory within a BAR file (bar file could be a debug token or application). You can extract that file using an archive utility such as WinZip.