05-10-2011 12:47 PM
Running into an error when trying to deploy an Unsigned application on a Playbook,
result::failure 500 BarFileUnsignedError
To simplify the debugging I grabbed the MenuBar sample from
Compiled it with a slightly modified config.xml, just added the <author> and <authorId> tags
<?xml version="1.0" encoding="utf-8"?>
<widget xmlns=" http://www.w3.org/ns/widgets"
<description> Sample that demonstrates how to create your own menu bars within a BlackBerry WebWorks application for Tablet OS</description>
<feature id="blackberry.app.event" required="true" version="18.104.22.168"/>
<access uri="http://www.blackberry.com" subdomains="true"/>
This is the deploy command
I:\Program Files\Research In Motion\BlackBerry WebWorks SDK for TabletOS 22.214.171.124\bbwp\blackberry-tablet-sdk\bin>blackberry-
Sending Install request...
Info: Action: Install
Info: File size: 64519
Info: Installing ...
Info: Processing 64519 bytes
result::failure 500 BarFileUnsignedError
I think my issue lies in the config.xml and blackberry-tablet.xml files, the documentation is not very clear on the requirement of these files.
Where do the <author> and <authorId> tags belong?
My blackberry-tablet.xml file contains
Solved! Go to Solution.
05-10-2011 02:40 PM
Got to be joking...got it to work my problem was I followed the instructions to a tee.
The instructions say
Configure your application for use with a debug token from the command line
The BlackBerry® Tablet OS allows you to run unsigned applications on a BlackBerry® tablet that has a debug token installed. To load an unsigned application you must configure the application's author and authorIdproperties match those of specified by the debug token.
blackberry-airpackager -listManifest <path to debug token>
You can now load your application on a tablet without signing it.
Package and deploy your application from the command line
4. blackberry-deploy -installApp -device <deviceIP> -package <BAR file path>
-password <device password>
That does NOT work...when you are compiling your application make sure the blackberry-tablet.xml is included alongside the config.xml etc files.
05-12-2011 05:04 PM - edited 05-12-2011 05:30 PM
My test blackberry-tablet.xml file contains only the following 4 lines but I have not used my actual company/author name or authorID. In case you don't know....you have to use the same author you used when you enrolled with RIM for your tokens, and you get the authorid from running the "blackberry-airpackager -listManifest " command.
The instructions are really good, except for the "Package and deploy your application from the command line" section where it states
Navigate to the folder where your application and XML configuration files are stored.
Type the following command to package, deploy, and launch your application from the command line.
blackberry-deploy -installApp -device <deviceIP> -package <BAR file path> -password <device password>
I found this does not work. For me unless I included the blackberry-tablet.xml file along side my config.xml etc when I compiled the application, the blackberry-tablet.xml inside the compiled .BAR file was a generic blackberry-tablet.xml file , ie the wrong data. So when I tried using my preconfigured blackberry-tablet.xml file at the time of deploy, as the instructions say, it had no effect as there was already a blackberry-tablet.xml inculded.
***However you could uncompress the .BAR file remove the blackberry-tablet.xml edit the MANIFEST.MF file to match your author and authorid values recompress, then the above instrutions were correct....Or you can uncompress edit the blackberry-tablet.xml and MANIFEST.MF inside the .BAR and compress...but really the instructions should say include the blackberry-tablet.xml at compile time, would save a lot of headaches as this writes the correct values to the MANIFEST.MF and includes the correct blackberry-tablet.xml file inside the .BAR
05-13-2011 11:31 AM
Are these instructions listed here still the ones to use? The ones on the website are still wrong? I find that hard to believe that bad instructions haven't been corrected.
05-13-2011 12:30 PM
05-13-2011 12:33 PM
I'll let you know once my manager figures out how to get me a real device. Right now I'm just simulating (though I've been studying the deployment instructions in great detail because I know that soon, really soon, I'll have a real tablet to test on...yeah...real soon...I can feel it!)
05-13-2011 12:42 PM - edited 05-13-2011 12:43 PM
Let be help your manager
THE SIMULATOR is not the same as the real thing. I had to fix my app when I saw it on the hardware the as scale was all wrong :-(