Android™ Runtime Development

[stewartt1982]

Hi,

This is my first attempt an porting app from Android to the Playbook ... so far everything has proceeded well.  

I have set my playbook into developer mode, I've received my signing key and registered it. From this I've created a debug token and deployed it to the playbook... all too easy.

I'm at the point where I am using the Command line tools to convert my apk to a bar file, and am getting the error

"[ERROR] [Apk2bar] Not a proper blacklist file: debugtoken.bar" from apk2bar using the command:

sh blackberry.tools.SDK/bin/apk2bar -d debugtoken.bar my_app.apk

If I try creating the bar file without the debug using:

sh blackberry.tools.SDK/bin/apk2bar   my_app.apk then I can create the bar.  Of course this fails upon deployment with:

sh blackberry.tools.SDK/bin/blackberry-deploy -password pass -installApp 192.168.1.158 my_app.apk
Info: Sending request: Install
Info: Action: Install
Info: File size: 3715188
Info: Installing ...
Info: Processing 3715188 bytes
actual_dname::
actual_id::
actual_version::
result::failure 881 required signatures missing (RDK, AUTHOR)

sh blackberry.tools.SDK/bin/blackberry-signer -verify -verbose debugtoken.bar  gives:

680 Wed Feb 22 03:02:48 EST 2012 META-INF/MANIFEST.MF

312 Wed Feb 22 03:02:48 EST 2012 META-INF/AUTHOR.SF
730 Wed Feb 22 03:02:48 EST 2012 META-INF/AUTHOR.EC
312 Wed Feb 22 03:02:48 EST 2012 META-INF/PBDT.SF
280 Wed Feb 22 03:02:48 EST 2012 META-INF/PBDT.EC

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.

--------------------------------------------

Can anyone point me in the correct direction to solve this?  If I understand correctly the debugtoken.bar file is OK, and my app is as well (checked with apk2barVerifier).

[mattdonders]

If you used Eclipse to write your Android app I found it much easier to install the Blackberry SDK into Eclipse. This lets you right click on your project and "Sign for App World" which exports a signed BAR for you.

Just a thought.

[stewartt1982]

Does Eclispe do something different? or in the end is it calling the same routines?

I'd rather not be forced to use eclipse unless I really have to.

[mattdonders]

---

stewartt1982 wrote:

Does Eclispe do something different? or in the end is it calling the same routines?

I'd rather not be forced to use eclipse unless I really have to.

---

I am going to assume it does the same thing the Command Line does, but can't be 100% sure. Sorry.

[stewartt1982 · Accepted solution]

I think I've fixed my problem ... I've now been able to deploy the unsigned app.

using this command :

 sh blackberry.tools.SDK/bin/apk2bar Mmy_app.apk -a stewartt -d debugtoken.bar