1. I saw you venting on Twitter this morning about this. I was hoping you’d wrap up your notes in a blog post. Thanks.

    1. I hope they are useful for someone. Looked all over for “keytool error: java.io.IOException: Incorrect AVA format” with 0 results! Lucky guess :/

  2. jasonlawl

    You’re not the only one who had a little problems getting the code signing to work. =] Had to read through the signing documentation more than a few times carefully to finally get it to work. (It’s relieving when it does!) haha

  3. Mohammed Kayyali

    Hey, do you know if the 480 x 480 image MUST to be the same as app icon ? or i can add a screenshot for the application ?

  4. Sukhrob

    Hi Joseph,
    Thank you for step by step instructions. I have the same situation as you do, but i still use Flash Builder Burrito. Can please provide some instruction on how to sign your app via Adobe Flash Builder Burrito. I have the .csj file.
    Thank you,

      1. Sukhrob

        Would you know by any chance why it gives me the following error in first step:
        Exception in thread “main” java.lang.UnsupportedClassVersionError: ….

          1. Sukhrob

            Thank you Joseph,
            Your instructions helped.

  5. zeth

    at first great blog.

    personaly a got an issue with the command line explain in the rim documentation
    blackberry-signer -verbose -cskpass
    -keystore -storepass

    i don’t find this line in you post , do you think it’s really neccesary?

    1. That option is to “Ask the RIM signing authority to sign your application” – I didn’t use it but opted for choice 2. I must have done it okay as all 3 app updates were approved yesterday :)

      1. zeth

        thank you very much for your answer. i was thinking almost the same thing. i’ve take a look at your applications on the appworld, i hope i’ll be able to try them in real with the playbook.

        1. zeth

          i forgot the soon … i hope i’ll be able to try them soon in real with the playbook.

  6. I think the correct dname parameter format is -dname “cn=”. For me worked like charmed.

    Regarding signing from Burrito – it doesn’t seem to work : it generates an empty bar.sig file…

    1. Yeah, this is not worked into Flash Builder at all. Needs to be done via command line.

  7. Lou

    Nice walkthrough, the signing process has been a huge pain! Multiple errors, some of the same I’ve received. But I’m stuck on this one and can not seem to get around it.

    Application-Development-Mode in Manifest is present and is not set to [false]

    There is some docs in the forums about it, but I have not gotten anywhere. Maybe in the next release of the SDK, it will be better.

  8. I’m getting error when signing playbook app using command line in windows vista, it could’nt connect with RIM server. When using command line in windows xp, the signing process is works like charm.

  9. Yeah, I went through the whole mess and got it working, and I still have no idea what it’s doing. And that bugs me. The whole playbook signing thing inspired my comic of a couple of days ago http://angriestprogrammer.com/comic/magic_processes :)

    Anyway, one question. Did you generate a different .p12 file for each app? I have two apps in the store that I need to sign and update (as you did) and one signed app that I’m about to submit. I just don’t know if a .p12 file is local to the company or to each app.

    1. Nope. I used the same cert for each of the 3 apps that needed to be signed.

      With that said- my understanding is that you need a separate cert for Tablet OS than for Android, so you cannot use the same .p12 for everything. Just for the same platform.

  10. Anthony Brown

    for those of you that got lost at what happened in step 9 with the error:
    //must update the in the -app.xml to InsertFileNameHere.swf

  11. Derek Manns

    Thanks for the information on this. I was wondering where you acquired the .csi password? I only have the one “pin” password when I applied for the key.


    1. You use the initial PIN along with the .CSJ that RIM sends you. When you create a RIM authority cert based upon that .CSJ, you will need to define a password just as you would when creating a self-signed cert.

  12. In 8), you need to enter -dname “cn=[Company Name]” – that’s how I solve it on Windows.

  13. Sorry I meant 7) (to create the p12 cert)

  14. Salman

    I have been searching the answer for this error for 2 days and wasn’t able find a solution!
    I have an app developed in flash cs5, AIR 2.5 with 1.0.0 as the version… I have the certificate file generated without any problems. But for some reason, I am not able to generate the .bar file!!!!
    the blackberry-airpackager gives me the following error:
    error 102: Invalid namespace http://ns.adobe.com/air/application/2.5
    Error: AIR validation failed

    Please HELP!!!

  15. Gorkem

    Hey Joseph;

    I am trying to sign my application, I got the BlackBerry BarSigner tool to register with the Signing Authority. When I try to execute command “blackberry-signer -csksetup -cskpass”. I got an error, ” ‘java’ is not recognized as an internal or external command, operable program or batch file.”

    Do you have an idea for the reason?

    Thanks in advance.


    1. You probably don’t have Java registered in your system PATH environment variables. So when the signer attempts to invoke it, it cannot be found.

      1. Gorkem

        Thanks Joseph;

        Registering path environment variables actually worked great!!

        I have another problem with signing at last step. While I am “Generating Key-pair”, I execute command “blackberry-keytool -genkeypair -keystore QNX.p12 -storepass PIN -dname “cn=XXX” -alias author”.
        I got an interesting error
        Error: null

        Nothing else is written just Error: null

        Thanks for help again, I will be appreciated if you have some opinions about the last error.


  16. Siddharth Jhanji

    Thanks..very helpful post..solved my problem..gud work..

  17. Yeah!

    Tnx man, your recap makes me happy!

    1 night without sleeping …..

Comments are closed.