BlackBerry Signing Tool for Tablet OS Now Live


BlackBerry PlayBook tablet

The deadline for the free BlackBerry® PlayBook™ tablet offer is fast approaching. Whether you have already submitted your app or you plan to do so soon, your app will need to be signed before it can be accepted into BlackBerry App World™ storefront.

We’re excited to announce that you can now sign apps using the latest version of the BlackBerry® Tablet OS SDK. Below is a quick overview of how to get started with application signing on the BlackBerry Tablet OS. Be sure you have installed the most recent version of either the BlackBerry Tablet OS SDK for Adobe® AIR®, or the BlackBerry® WebWorks™ SDK for BlackBerry Tablet OS. You can download the latest version of either SDK from the BlackBerry Tablet OS Application Development site.

Before you start signing your application, you have to register with the Research In Motion® (RIM®) Signing Authority. Fill out the web form – registration is free, but you need a credit card to complete the registration process. A $1 hold will be placed on your account to verify the credit card. The hold is released after your credit card company accepts the transaction, and the hold will not appear on your monthly bill. When the registration process is complete, you receive a CSJ registration file via email.

There are two phases to the signing process: configuring your computer, and signing the application. You only need to configure your computer once. To configure your computer:

  1. Initialize communication with the RIM Signing Authority: The signing tool is designed to prevent tampering and eavesdropping on information it exchanges with the RIM Signing Authority.
  2. Register your CSJ registration file with the RIM Signing Authority: Once you have initialized the communication channel, you can register your CSJ file, which uniquely identifies you to the RIM Signing Authority.
  3. Ensure that you have a Developer Certificate: You can use the signing tool to create a developer certificate, or provide your own. If you create a Developer Certificate using the signing tools, ensure that the common name (company name) parameter matches what you enter in the Company field on the registration form. If you have an existing Developer Certificate you use to sign your Adobe® Flash® applications, ensure that the name you enter in the Company field on the registration form matches the common name (company name) of your existing certificate. You will not be able to sign your BlackBerry Tablet OS Application if these names do not match.

Once your development environment is configured, you’re ready to sign your application:

  1. Request a signature from the RIM Signing Authority: Use the signing tool to request that the RIM Signing Authority applies a signature to your application.
  2. Apply your signature: Use the signing tool to sign your application using your Developer Certificate.

You now have a signed application that you can upload to BlackBerry App World for distribution to customers or other users. For more information about using BlackBerry App World, see the Vendor Portal Administration Guide.

For detailed instructions, see the following documentation:

  • BlackBerry Tablet OS SDK for Adobe AIR: you can sign your application using version 0.9.3 or higher of the SDK. See Signing your application in the BlackBerry Tablet OS SDK for Adobe AIR Developer Guide for more information.
  • BlackBerry WebWorks SDK for Tablet OS: you can sign using version Beta 2 or higher of the SDK. Please see the BlackBerry WebWorks SDK for Tablet OS Development Guide for more information.

Time is running out. Submit your app today!

About Ricardo O.

Ricardo is a writer on the Developer Documentation team at Research In Motion (RIM). After he started coding and using Visual Basic, Ricardo couldn't stop thinking about how computers and people relate to each other. He even helped design a conversational speech interface for email. Ricardo loves funneling his experiences into helping the BlackBerry developer community create great Java and Flash applications for BlackBerry smartphones and the new BlackBerry PlayBook tablet.

Join the conversation

Show comments Hide comments
+ -
  • RIM Makes BlackBerry Code Signing Keys Free for Tablet and Smartphones | BlackBerry Cool

    […] even need a signing key. Perhaps the next step will be to do away with the signing keys altogether.Read more over at the BlackBerry Developer blog.Related Posts:Developer Tip: Transfer RIM Signing Keys to a MacReview: QR Code Reader Code Muncher […]

  • RIM Announces Code Signing Keys Free for PlayBook & Smartphones | PocketBerry

    […] To start signing applications, make sure you register with the RIM Signing authority by filling out their web form.  It is free but RIM holds $1 on a credit card to verify it is valid.  You get your buck back after your credit card company processes the transaction.  Not so sure what that’s all about but that’s what’s required.   You can read more about it at the BlackBerry Developer’s Blog. […]

  • J. Rab

    hey Ricardo,

    Great article! I just want to add that maybe you should include that all this must be done via command line either through Terminal (Mac / *nix) or through Command Prompt (Windows). A lot of people are confused as to whether or not they should use the IDE’s (Flash Builder 4 / Flash Builder Burrito). If you use the IDE’s, they are quite misleading because they do not throw any errors to the user even when there should be. Just a thought!

  • chall3ng3r

    Hello Guys,

    I’ve been trying to register for last couple of days using my pre-paid credit cards. I always get “Order Creating Failed”. I have sent email to support as well. But no reply so far. There should be PayPal option was well.

    My first Playbook app is ready just need to sign. Or should I just upload the app without signing for now?


    // chall3ng3r //

    • Oraclecomlink

      chall3ng3r, if you’re worried about not being able to get your pre-paid credit cards working and signing your .bar release before the due date, I suggest you submit an unsigned version (just to be safe first) – then you have more time to figure out how to get the pre-paid card working.

      • chall3ng3r

        Thanks. I was planning exactly same. But I ended up by using a friend’s master card, which worked on first try. I’m now just waiting for email from Blackberry with my keys.

        // chall3ng3r //

  • BlackBerry Signing Tool For The Tablet OS Now Live – Code Signing Keys Now Free For Smartphone & Tablet OS! |

    […] BlackBerry PlayBook tablet offer. For more info and to register go to or read more at RIM’s Dev Blog. Posted in Apps & Games, Desktop & Server Software, News & Rumors | View […]

  • Scott

    I submitted my signed BAR file last Friday (2/18). I recieved the email telling me to resubmit signed files today. Is any action required on my part?

    • J. Rab


      if your submission was signed, then no action is required. the email was only for those who haven’t submitted a signed version yet.

      • Scott

        Thank you. RIM should be more straightforward about these things.

  • Alex

    It’s not nice, that I can only register with a valid credit card. Not all people have a credit card. AppWorld has a Identification-Form, my PayPal Account. Why change the process to credit card? To get a credit card takes here in germany more than a week.

  • Pete Austin

    You Win, RIM! (An Open Letter To RIM’s Developer Relations)

  • RIM Addresses Some Developer Question Regarding App World and Other Requirements - BerryReview - Mobile Edition

    […] tablet.The Signing Keys Questions On Tuesday February 23rd, we announced the availability of the BlackBerry Signing Tool for the BlackBerry PlayBook tablet,and we’ve since received a number of questions about what this […]

  • stolex

    I’m developer from Serbia, but on your Sign page Serbian isn’t in country list, only Yugoslavia. Yugoslavia doesn’t exist about 10 years. My Visa card is registered on Serbia, and I can’t get key. I asked your devsuport, but there are no answer :(

  • brahimi

    We already have a key to sign Java apps for Torch, Storm, Bold, etc. do we still need to get another key for playbook or can we use that? if we can use the old key, is there a special process for that?

    • Anonymous

      Unfortunately, you need to obtain a new set of keys. With the BlackBerry PlayBook and the new file format (.bar file instead of .cod file) we had the opportunity to improve upon the existing signing process and information. The side effect was that this required a new set of keys that contained more information (company name).

  • BlackBerry Signing Tool for Tablet OS Now Live | Inside BlackBerry

    […] Read more at the Inside BlackBerry Developer’s Blog » […]

  • Phuong

    Hi there, I’ve filled out the web form as mentioned above and I got my order confirmation, but it’s been a while (more than 10 days now) I have not receive any email so how do I sign my apps?

  • Chris

    I followed all these instructions and submitted my app. Now, a day later, I received an email saying that I have to resubmit and append “_signed” to my app name. I’m confused as to whether or not this is a real requirement or something that doesn’t apply to my app because I already signed it appropriately when I first submitted.

    If it is indeed a requirement to name my app “”, then it would be nice to include that information in this post, because I would have done that originally, had I known it was a step in the process. Seems stupid to only find out about this step after I’ve already submitted.

  • timdw5s

    I am confused too….what do you mean by resubmit with _signed? When signing it produces a .bar file and a .bar.sig file. I tried to upload the .sig file and it wouldnn’t let me even in a .zip folder. So I zipped the .bar and the .bar.sig and uploaded both…this is confusing… Please advise.

    • Mike Kirkup

      I apologize for any confusion. If your bar file is signed you do not need to upload it again or change the name of it to match a signed convention.

  • benji

    RIM needs to streamline things a bit. First and foremost, don’t send the panic-inducing email to people who already signed their apps, leaving them to second-guess whether they might have screwed up the app-signing process.

    Which brings me to my second point: streamline the tools! The app-signing process is waaaaay more complex than it needs to be. There should only be two steps: (1) Request certificate from RIM, and (2) apply signature to compiled app.

    The five-step process (initialize comms with signing authority; register CSJ; ensure valid cert; request signature; apply signature) is preposterous and error-prone.

blog comments powered by Disqus