PlayBook Debug Tokens and Signing

The process for developing and deploying applications to the PlayBook simulator is a little different then that of the device. For the simulator you simply place it into development mode and you can deploy your un-signed applications. There are 2 additional steps that you need to do in order to deploy and debug your applications on the device.

The first step is to create and upload a debug token to the device. This entire step can be done with the command line, but is much easier to do with the Flash Builder plugin. Before you can create your debug token you must sign up for signing keys. This can be done from the BlackBerry Developer Zone form found here. You should get your keys the following day so may sure to sign up for your keys early so you aren’t waiting a day to develop for the device. What the debug token does is associates your application with you and your device. Watch the video below for a complete list of steps on how to create and upload.

The second thing you need to do is add the author and authorId tags to your blackberry-tablet.xml file. This associates your application with your debug token and allows it to run on any device with that debug token installed on it. With this you should be able to deploy your application to your device as many times as you need.

The alternative to using debug tokens is to sign your application every time you want to load it on to the device. This would mean that for every little code change it would need to be re-signed. There are 2 things to keep in mind when signing your application. The first is that the version number has to be incremented every single time you sign your application. If you try to sign an application with the same version number it will throw an error. You can read this page for more information about assigning a version number to your application. The second thing to keep in mind is you need to be connected to the internet in order to sign your application. Having to do these 2 things every time you wanted to test your application on the device is unreasonable, which is why debug tokens were created in order to provide greater flexibility in developing and deploying to the actual device.

If you have gone through and followed all the steps in the video below for creating debug tokens, your applications is all ready to be signed. It is as simple as right clicking on the project and selecting Export. I hope the video below helps you get your application on deployed to the device.

PlayBook Debug Tokens and Signing from Julian Dolce on Vimeo.

Continue reading » · Written on: 04-24-11 · 11 Comments »

11 Responses to “PlayBook Debug Tokens and Signing”

  1. Calin wrote:

    hi Julian,

    I’m following the steps presented in this video and unfortunately I’m getting the following error:

    “Unable to parse issue date from debut token”.

    Any help would be greatly appreciated.

    Regards,
    Calin Pleava

    April 25th, 2011 at 7:51 pm
  2. Julian wrote:

    Hi Calin,

    This issue comes up if the Java being used by Flash Builder is different than the one in your user path. The workaround is to make them point to the same Java install.

    I am trying to get the exact steps to solve this. Will update here when I do.

    April 28th, 2011 at 9:42 am
  3. Aswathy wrote:

    Hi,
    I am having difficulty to actually create the token. I use the command they give but it gives me this error:

    barsigner error: server error: The signature on this code signing request didn’t verify. The likely reason of this problem is entering an incorrect CSK password.

    But i’m sure that i have used the correct password .
    Because I used the same password for registration and it was successfull.Can anyone help to solve this issue

    Thanks

    May 4th, 2011 at 3:23 am
  4. Matthias Wille wrote:

    I came across the “Unable to parse issue date from debut token” problem too. It is an issue with non en_US environments from what I figured out.

    There are two workarounds which I explained here…

    http://flexdomino.blogspot.com/2011/05/playbook-signing-2ndcreating-and.html

    May 17th, 2011 at 3:11 am
  5. @renaun posts: PlayBook (.bar) Application Signing Roundup wrote:

    [...] RIM’s docs on signing your application with Flash Builder 4.5. My note here is read through all the doc pages first before starting and pay attention to the notes and details. RIM’s documentation on debug tokens. Julian Dolce showing off debug tokens and how they work [...]

    June 3rd, 2011 at 1:14 pm
  6. Raymond Camden wrote:

    Am I right in thinking this line, ” What the debug token does is associates your application with you and your device.” implies that the debug token is _per_ app? So if I wanted to quickly demo something or do a quick test, I can’t just use the same debug token for a new app? I guess I could make one app I call Test and use that for ad hoc device testing if so.

    June 21st, 2011 at 9:52 am
  7. Julian Dolce wrote:

    @Raymond

    The debug token isn’t per application. You can use the same debug token for as many applications as you like. The debug token is really per author. You can have the same debug token on different devices as long as you specify all of the different PIN’s when creating it.

    Hope that clears it up for you.

    Cheers
    Julian

    June 21st, 2011 at 9:59 am
  8. Raymond Camden wrote:

    Thanks. Btw – your blog doesn’t offer email notifications on new comments? I’d add that. :)

    June 21st, 2011 at 10:48 am
  9. PlayBook (.bar) Application Signing Roundup | FlexHero wrote:

    [...] RIM’s docs on signing your application with Flash Builder 4.5. My note here is read through all the doc pages first before starting and pay attention to the notes and details. RIM’s documentation on debug tokens. Julian Dolce showing off debug tokens and how they work [...]

    June 22nd, 2011 at 11:44 am
  10. Halapino wrote:

    I keep getting errors that my credentials don’t match. Is that a problem with my key, certificate or token? I think I’ve been using different author names and am waiting for new signing keys to test that out, but everything else was exactly as you did it in your walkthru video.

    Halapino

    July 4th, 2011 at 11:59 pm
  11. playbook ref | code@butterflybone wrote:

    [...] token (on simulator) http://deleteaso.com/playbook-debug-tokens-and-signing/ This entry was posted on Sunday, February 12th, 2012 at 1:06 amand is filed under mobile. You [...]

    February 11th, 2012 at 12:09 pm

Leave a Reply