12-20-2011 08:34 PM
Getting the App author doesn't match debug token author error, as seen below.
>blackberry-deploy -installApp -password xyz123-device 10.251.221.230 -package h:\html\webworks\hello\out\hello.bar
Info: Sending request: Install
Info: Action: Install
Info: File size: 3618419
Info: Installing ...
Info: Processing 3618419 bytes
result::failure 500 Application author does not match debug token author.
I have been using Ripple to package and sign, and the command-line above to deploy to an actual tablet.
I have read some of the other threads on this topic, but many of them refer to files that I don't mess with, such as blackberry-tablet.xml - I assume that Ripple adds that as part of packaging. Hopefully I don't have to manually fix up this file every time I package.
I dumped out the generated air/blackberry-tablet.xml file, and it has <publisher>Sample Inc.</publisher>, but no <author>.
What values in what files are being compared to detect author mismatch?
All very confusing. Hard to have a clear mental map to visualize the end-to-end process.
12-20-2011 08:36 PM
12-20-2011 08:59 PM
No luck messing with the blackberry-tablet.xml file. Extracted it from the application .bar, added
and changed <publisher> to contain the same text, and repackaged into the .bar file.
Here's my META-INF/MANIFEST.MF from the debug token .bar file:
Archive-Created-By: BlackBerry BAR Packager v1.4
Package-Author: Example International
Also, I just noticed that I am posting in the Adobe Air group, probably should have been in the Web Works group.
12-20-2011 09:02 PM
12-20-2011 09:03 PM
12-20-2011 09:15 PM
I missed the authorId. Just copied the value out of the debug token MANIFEST.MF's Package-Author-Id field and pasted it (see below), but still getting the error.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><qnx>
<!-- These environment variables hide the browser context menu -->
<env value="false" var="WEBKIT_TABS_SUPPORTED"/>
<env value="false" var="WEBKIT_CONTEXT_MENU_SUPPORTED"/>
<env value="false" var="WEBKIT_SELECTION_SUPPORTED"/>
<env value="true" var="WEBKIT_WEBGL_SUPPORTED"/>
<!-- Explicitly set the Webkit graphics buffer to reduce memory usage. Will be reduced post-rtm to 3 or 0. -->
<env value="6" var="WEBKIT_NUMBER_OF_BACKINGSTORE_TILES"/>
12-20-2011 09:23 PM
Okay, so if you have that debug token loaded (plz check if not certain), then it "should" be working at this point.
Mine looks similar, but with only the <publisher> and <authorId> lines. I doubt the redundancy with <publisher> and <author> is your problem though.
I think you should take your .bar file and unzip it, and inspect the MANIFEST.MF file that's being generated. Those two lines should be getting generated from the blackberry-tablet.xml file, so they should now match what the debug token's MANIFEST.MF has in it.
Stray/long-shot idea: recently the SDKs have been migrating to use bar-descriptor.xml instead of blackberry-tablet.xml. Any chance that's been done in the latest WebWorks SDK, and that it's not actually picking up your bb-tab.xml any more? (Inspecting the MANIFEST.MF is conclusive though... the .xml file is not actually used on the PlayBook, as far as I know, but only during packaging to populate the manifest file. What you see there is what matters.)
12-21-2011 06:23 PM
Made some progress. When I run a build and package from the Ripple interface, both the MANIFEST.MF and blackberry-tablet.xml have the author set as "Sample Inc."
Package-Author: Sample Inc.
So that's definitely a mismatch with my debug token, which I registered as "Example International".
I found that if I manually update the application.bar file to make MANIFEST.MF and blackberry-tablet.xml match the debug token info, then I get a signature failure:
result::failure 500 air/blackberry-tablet.xml: SHA512 digest mismatch
So what's the best course of action? Reregister for another debug token with a different name? Find the place in my current installation (where??) that is packaging the author information and change it?
12-21-2011 07:22 PM
12-22-2011 10:40 AM
You definetely to ask this on webworks forum, they should have solved it some-how by now. I don't think
their tool read blackberry-tablet.xml so it must be another way how you suppose to set this info