10-07-2013 02:36 PM
I'm trying to manually sign my 10.1 SDK built bar file using the following which returns "Bar Signed" when run.
howver when I try and publish it to Blackberry world I'm getting the following error upon uploading it.
"Bar is Not AUTHOR Signed"
Solved! Go to Solution.
10-07-2013 02:59 PM
blackberry-signer -storepass $MYPASS$ MyApp-1_0_0_5.bar
That should be all you need, assuming your BlackBerry ID Token and author.p12 are in the default locations.
10-07-2013 08:17 PM - edited 10-07-2013 08:58 PM
that seemed to have resolved the problem for Vender "A" however the same problem exisits with the other vendor "B". If I rebuild Vendor "B" app using the 10.2 sdk and let the ide sign then it works fine, however if I build for 10.1. SDK and manually sign then it doesn't work for Vendor "B" and I am gettng the same error "Bar is not AUTHOR Signed"
This is very frustrating any help would be greatly apprecuated. I'm not sure what I could have done wrong. I created a new developer cert for Vendor "B"., and downloaded the appropriate BBIDToken.csk from within the ide, same as I did for vendor "A" which is working, the only difference between Vendor "A" and Vendor "B" is that vendor "A" used to use the code signing keys, however I assumed that using the command link I could properly link a 10.1 sdk build using just the author.p12 and bbidtoken.csk
10-08-2013 08:47 AM
Before building the application did you change the author.p12 the IDE is pointing to? Go to Window, Preferences, expand BlackBerry click on Signing. Is the correct Developer Certificate with correct vendor B info listed?
10-08-2013 09:03 AM
I actually did a Restore from the same dialog window,upon which I saw that the devloper cert changed to reflect Vendor "B", If I rebuild for 10.2 SDK and let the ide do the code signing then everything works. IF I puclish fr 10.1 and manaully sign from the command line then no error messages until I upload to Blackberry world.
As I've yet to publish anything for real for vendor "B" I could try and recreate a new developer cert and also redownload the BBIDToken.csk if you think that would help.
P.S. if I rename the .bar to .zip on the file that is giving the no AUTHOR name error and then look into the manifest.nf I do infact see something within the Author name and id. which reflects vendor "B"
10-08-2013 09:17 AM
Could the fact that Vendor "A" has both older code signing keys and bbidtoken.csk installed and Vendor "B" only relying on the newer BBIDToken.csk be doing something the mess up the manual code signing of 10.1 sdk build .bars?
not sure but thought I would just mention
10-08-2013 09:25 AM
In 10.2, if the BlackBerry ID token exists it should use that over the barsigner.csk and barsigner.db files.
Can you run this command on a bar file where you are getting the author signed error and paste the output (censor the filenames if you like).
blackberry-signer -verify -verbose filename.bar
10-08-2013 10:06 AM
Sorry it was my mistake, I forgot to remove the RDK option from the second bat file which I had created for vendor "B" now that I have removed it I'm not longer getting any error..
Thanks so much for your great, dedicated , and superb support..
10-08-2013 10:26 AM