06-03-2011 04:24 AM
I've had some weird problems that nobody else has mentioned regarding information in the blackberry-tablet.xml file and the subsequent bar file manifest. I'm using the command line tools in linux.
Here is my file for reference:
<qnx> <icon> <image>blackberry-tablet-icon.png</image> </icon> <author>My Author Name</author> <authorId>My Author Id</authorId> <category>core.games</category> <action>play_audio</action> <buildId>1</buildId> <platformVersion>184.108.40.206</platformVersion> </qnx>
The first problem is that even though I specify the category, it does not end up there when run on the actual device. This is true for both testing unsigned with a debug token and for the app downloaded from AppWorld.
The second problem has to do with testing the unsigned bar and debug tokens and such. I get the "500 BarFileUnsignedError" even though I'm following instructions to the letter. Here's the output (notice the "actual_" items are blank), and after that I'll put the command I'm calling.
Info: Package created: shipgame.bar Sending Install request... Info: Action: Install Info: Development mode: on Info: File size: 3755841 Info: Installing ... Info: Processing 3755841 bytes actual_dname:: actual_id:: actual_version:: result::failure 500 BarFileUnsignedError Sending Launch request... Info: Action: Launch Info: Development mode: on Info: Launching athrainstorm.testYXRocmFpbnN0b3JtICAgICA... result::130179179 Info: done
Here is the command line that generates the above output:
blackberry-airpackager -devMode -package shipgame.bar -installApp -launchApp shipgame-app.xml shipgame.swf blackberry-tablet-icon.png -device 192.168.2.3 -password pass
The manifest has this value:
which tells me it's not getting the value out of the blackberry-tablet.xml file.
I discovered that if I supply the airpackager command with my debug token bar file that the correct information is put into the manifest. Here's the command:
blackberry-airpackager -devMode -debugToken /path/playbookDebugToken.bar -package shipgame.bar -installApp -launchApp shipgame-app.xml shipgame.swf blackberry-tablet-icon.png -device 192.168.2.3 -password pass
And the resuting "actual_" items:
gICA actual_id::testYXRocmFpbnN0b3JtICAgICA actual_version::220.127.116.11
With the correct results in the bar manifest file also. When I do things this way, all works as it is supposed to, except for the app category.
My blackberry-tablet.xml file is in the same folder as all of my other files (app.xml, app.swf). What am I missing here?
06-03-2011 08:08 AM
06-03-2011 01:50 PM
Wow, I don't know how I missed that. At some point I thought that the file needed to be named blackberry-tablet.xml because the packaging tool automatically includes that file. Whoops. It's actually pretty amazing that I was able to submit an app, have it accepted, and put in appWorld without that config file. I guess it's that the packager tool has parameters for the things that are required from the xml file, and I figured those out, but somehow missed including the xml file itself.
Thank you. I will test this out later, but I feel pretty confident that it will work now.