07-23-2008 05:35 PM
I am back-porting a 4.2 application to 4.0. I copied the sigtool files from the 4.2 JDE "bin" directory to the 4.0 JDE "bin" directory. However, when I attempt to sign the COD files, the operation fails. The "detail" says:
"The signature on the code signing request didn't verify. The likely cause of this problem is entering an incorrect password."
The password is correct, and verified several times. Is there some other reason for this to fail? Am I missing a step when moving the sigtool files from 4.2 back to 4.0?
The original JDE (that the app was developed on) was 4.2.1. The one that I'm trying to sign on is 4.0.2.
Solved! Go to Solution.
07-23-2008 06:26 PM
07-23-2008 06:31 PM
What I would do is install JDE 4.3 (or greater) so you can get the "-p" switch with SignatureTool (which allows you to provide a password on the command line). Then either copy your sigtool.* files over, or request new keys from RIM. Then, use the new SignatureTool to do all your code signings - it will work with all older versions of the JDE.
In my build system I have one property pointing to the OS I'm developing for and one property always pointed at my 4.3 install which I use to sign all my artifacts.
07-24-2008 09:09 AM
Update on this issue: I got the sigtool files from another (older) machine, from the 4.0 JDE/bin directory, copied them into my new 4.0.2/bin directory, and all is well.
My (unsubstantiated) conclusion is that you can move these files "up" level to a newer JDE version, but moving "down" level is not guarenteed to work because there have been some file changes made between 4.0 and present.
Perhaps RIM folks might have an official ruling on this.
07-24-2008 12:01 PM
This link explains the changes that occured in version 4.3.0. This is the only version of the BlackBerry JDE/Component Pack where the format of these files changed.
What Is - Signature Key format changes in BlackBerry JDE 4.3.0
Article Number: DB-00639