09-23-2013 08:32 AM
This is the message I get since yesterday. 3 days before everything was fine.
out: [ERROR] Error: The signature on the code signing request didn't verify.
The likely cause of this problem is entering an incorrect CSK password.
And no, I did not change the password, I have reentered my password many time, I have checked the password, I have copied the password from a backup txt file and pasted it and always the same result.
I am sitting here, have a job to do and can not finish it because of this error.
time is money and time is running.
so, what's up?
09-23-2013 02:40 PM
Have you done any Java updates lately? I have seen issues like this in the past when a 64bit of Java is used istead of 32bit. May be worth double checking?
09-23-2013 06:32 PM
working on windows 32bit with canary chrome and had no java update the last days.
as I said: it was working 4 days ago and suddenly I get the message wrong CSK password.
09-25-2013 01:12 AM
09-25-2013 03:14 AM
this is the worst answer I could get.
You know 10.2 is just a few days away, I have to update paid apps, but I can't because of this error.
If you read the first message from me than you will see I tried it in different ways, I tried it manually, with script and many other things, too.
last changes on barsigner.db and barsigner.csk are from 09/02/2013.
As I said before: Everything was running smooth til friday, 09/20/2013 and this message poped up suddenly and without changes.
I tried that way too yesterday: http://devblog.blackberry.com/2013/08/code-signing
But here I get the message: blackberry-signer order is misspelled or missing.
So, what else.
Kick all users who paid for apps with the launch of 10.2?
09-25-2013 03:43 AM
09-26-2013 08:35 AM
The blackberry-signer is missing or not found error means Windows cannot locate that file. It's not in the path and not in the current directly you are running it from. When running the command, change to the directory where it exists. It should be in the dependencies\tools directory found under your installation directory.
Can you try to create a debug token with your previous keys and let me know if you get the password error there?