11-23-2012 12:02 AM - edited 11-23-2012 12:02 AM
I am trying to deploy my signed .BAR application to my BlackBerry PlayBook but everytime I try I get this wierd error result::failure -103
These are the steps I am doing:
first comvert my .APK to BAR
./apk2bar [path to my apk folder] ~/android-sdks/ -t [path to output folder] -rv
then I sign it
./blackberry-signer -verbose -cskpass [password] -keystore author.p12 -storepass [password] [path to my .bar] RDK author
Then I verify it:
./blackberry-signer -verify -verbose [path to the .BAR]
and this is the output I get:
1342 Thu Nov 22 23:25:04 EST 2012 META-INF/MANIFEST.MF 608 Thu Nov 22 23:25:04 EST 2012 META-INF/AUTHOR.SF 601 Thu Nov 22 23:25:04 EST 2012 META-INF/AUTHOR.EC 608 Thu Nov 22 23:25:04 EST 2012 META-INF/RDK.SF 280 Thu Nov 22 23:25:04 EST 2012 META-INF/RDK.EC sm 7600 Thu Nov 22 23:24:16 EST 2012 android/res/drawable-mdpi/icon.png sm 169511 Thu Nov 22 23:24:16 EST 2012 android/Chmbrs-NotePadBB.apk s = signature was verified m = entry is listed in manifest k = at least one certificate was found in keystore i = at least one certificate was found in identity scope Info: Bar verified.
According to this everything is fine.
Finally I push the file to my PlayBook
./blackberry-deploy -installApp -device 192.168.1.109 -package [path to the .BAR] -password [Playbook password]
but this is where it fails and I get this output
Info: Sending request: Install Info: Action: Install Info: File size: 133672 Info: Installing ... Info: Processing 133672 bytes Info: Progress 50%... Info: Progress 100%... actual_dname::com.chmbrs.apps.notepad.gYABgOwP1jrt
FP9mlr5GwQ_xwlw actual_id::gYABgOwP1jrtFP9mlr5GwQ_xwlw actual_version::220.127.116.11 result::failure -103
I can see the application installed in the PlayBook but when I try to pen I get a window asking me to approve some permissions. I accept them and then I see a black window and the application closes itself. It does that all the time.
I have Oracle jdk installed version 1.6.0_33 and I am using Ubuntu 12.10 . That shouldn't matter though because according to the tool my .BAR is signed and without errors.
Any ideas why is not working? I would like not to use Eclipse because with the latest ADT update the BlackBerry plugin is broken and is not working not even on windows.
Thanks for the help.
Solved! Go to Solution.
11-23-2012 01:59 AM
Try these steps,
batchbar-deploy <input_files> <IP_address> <tablet_password>
11-23-2012 10:49 AM
If you open the batchbar-deploy file, in an editor, you will see that at the end it executes a blackberry-deploy command and I tried that approach already and it is still failing.
11-23-2012 11:00 AM
There is no documentation about that. I do not think the apk needs to be singed. I do bot remember doing that before. In the whole workflow either using command line tools or the Eclipse plugin no where it says that you need to sign your apk before signing the BAR file
Are you sure about that?
11-23-2012 11:12 AM
I'm 100% sure that I needed to sign the apk before signing the bar. However, I'm not 100% that I've got the -103 error when it was not signed. It could of been a different error code.
I'm sorry guys, but wouldn't be faster just to try that?
11-24-2012 06:33 PM
Yes! you were right!! it seems you need to sign the .APK before packing it and send it to your playbook for installation. I followed these steps and it worked:
Go to your android project root folder and build your project for release
ant clean and release
Connect to your Playbook:
./blackberry-connect [playbook IP] -password [playbook password] -sshPublicKey [key].pub
sign your APK with your keys:
jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore [your key].kestore [your app name].apk [alias]
--verify your signed apk
jarsigner -verify bin/NoteList-release-unsigned.apk
now if it passes, you can create the BAR file
./apk2bar [path to your APK folder] [path to android dsk folder] -t [path to output folder] -rv
Sign the BAR file
./blackberry-signer -verbose -cskpass [password] -keystore [path to your certificate].p12 -storepass [certificate password] [path to your BAR file] RDK author -- to verify the signed BAR ./blackberry-signer -verify -verbose [path to your BAR file]
And Finally sending to you Playbook
./blackberry-deploy -installApp -device [playbook IP] -package [path to your BAR file] -password [playbook password]
I tried these steps using Ubuntu 12.10 and CommandLineTools_1.3 beta. Just remember to turn development ON on you playbook and enable SSH access so you can use blackberry-connect. Also, when you download the command line tools you need to give the execution permission to all the scripts.
Hope this helps some one developing under Ubuntu until BlackBerry fixes the plugin for eclipse which is broken with the latest ADT tools rev 21.