Archive

Archive for January, 2012

Notes on running AIR apps on Blackberry playbook

January 11, 2012 Leave a comment

After several attempts to run my non-finished app on the playbook I find it usefull to save some notes on how to proceed step by step. So many examples that can be found over the web I know, I’ll add my contribution too because it took some time to deploy it the first time so one more described experience may not be useless.
Register for signing keys on Blackberry web site here:
[A]
It’s important to save somewhere the PIN that you enter here!

Signing Keys Order Form

Signing Keys Order Form

      Once ordered you will receive two signing keys by email

 

    They are called client-RDK-XXXXXXXXX.csj and client.PBDT-XXXXXXXXX.csj.
      signing with blackberry you CSJ file.

 

      If you did several unsuccessfull attempts before you need to delete your previous attempts with:

blackberry-signer -cskdelete

      For others fresh new developers register your RDK file like this:

blackberry-signer -cskpass YOUR_PASSWORD_HERE

      Now remember the step [A] where you entered y pin ? enter it again after csjpin here:

blackberry-signer -register -csjpin YOUR_PIN_HERE -cskpass YOUR_PASSWORD_HERE client-RDK-XXXXXXXXX.csj

    I have then received an email saying that my CSJ registration was ok.
    Them comes the P12 file creation:

blackberry-keytool -genkeypair -keystore YOUR_FILE_NAME.P12 -storepass ENTER_STOREPASS_HERE -dname "YOUR_APP_NAME" -alias author

To create a debug token I have executed the following commands:
blackberry-debugtokenrequest -register -cskpass YOUR_PASSWORD_HERE -csjpin YOUR_PIN_HERE client-RDK-XXXXXXXXX.csj

It said :

already registered

So I did:
blackberry-debugtokenrequest -register -cskpass YOUR_PASSWORD_HERE -csjpin YOUR_PIN_HERE client-PBDT-XXXXXXXXX.csj
It said :

successfully registered with server

The debug token is created with the following command: (replace 0x444444 with your device id)
blackberry-debugtokenrequest -register -cskpass YOUR_PASSWORD_HERE -keystore YOUR_FILE_NAME.P12 -storepass ENTER_STOREPASS_HERE -deviceid 0x444444 NAME_OF_YOUR_DEBUG_TOKEN_FILE.bar

debug token created

To upload the debug token on your device, press upload debug token and then execute the following command: (replace 192.168.0.14 with your device ip address)

blackberry-deploy -installDebugToken NAME_OF_YOUR_DEBUG_TOKEN_FILE.bar -device 192.168.0.14 -password YOUR_DEVICE_PASSWORD

Now you can install unsigned apps on your device. theoretically … you need to ensure that your bar file (the one for your app) contains the same info as the debug token:
List the debug token info like this:

blackberry-airpackager -listManifest NAME_OF_YOUR_DEBUG_TOKEN_FILE.bar
Copy Author and AuthorId in the appropriate fields in the blackberry-tablet.xml file, package your app as a bar file with these info:

blackberry-airpackager -package YOUR_APP.bar YOUR_APP.xml blackberry-tablet.xml YOUR_APP.swf -devMode

and deploy it on the device:
blackberry-deploy -installApp -device 192.168.0.14 -package YOUR_APP.bar -password YOUR_DEVICE_PASSWORD

That’s it. As I said it took time for me, especially the order of the commands and also to install the debug token. These are the commands which worked for me in the same order I runned them. I hope it helps!

Advertisements