12-22-2011 03:02 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.
Thanks to pointers from the good folks in another forum, I have found the mismatch. When building via Ripple emulator, the resulting .bar file has author and authorId set as "Sample Inc." I don't remember setting this value, and walking through WebWorks installer again I didn't see where I would have entered this.
Package-Author: Sample Inc.
When I registered my debug token, I used the name "Example International". That was on the web form.
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?
Where does WebWorks get the author info that it embeds in the .bar file's manifest.mf and blackberry-tablet.xml? Is there any way to change it?
12-22-2011 03:24 PM
You can always make as many debug tokens as you want if you have the signing keys.
As per the author, did you have an author element in your config.xml?
12-22-2011 04:45 PM
You can't change manifest.mf file and other files as well in the bar package, because it breaks cryptographic hash.
To fix the issue, after you generated debug token, edit bbwp.properties file located in Your Webworks SDK Location\bbwp\bin folder by entering the path to debug token: (i.e. <debug_token>......debugtoken.bar</debug_to
12-22-2011 07:12 PM
I didn't have an <author> element in config.xml, as I was just following the Getting Started example. But adding <author> element and rebuilding still results in the wrong Package-Author in MANIFEST.MF and <publisher> in blackberry-tablet.xml, and not surprisingly leads to the error message in the Subject line.
As a workaround, I can avoid the debug token scenario by creating a signed build.
I'm not sure I undersand the statement about creating debug tokens if I have the signing keys. As I understand the docs, you have to go through the web form request dance every time to create a new debug token, and any new token invalidates a previous token.
In any case, changing the debug tokens is too late in the process - seems like a band-aid. I need to understand where the whole author of Sample Inc. is coming from in the first place.
02-22-2012 02:59 PM
Could someone from RIM answer the original question.. ie where are these lines coming from and how do we fix them?
Package-Author: Sample Inc.
In my case I am not using Ripple, just the command line tools but I get the same error:
result::failure 881 application author does not match debug token author
02-22-2012 03:44 PM
Well I guess I can answer my own question. Edit bbwp/AirAppTemplates/src/blackberry-tablet.xml and add or edit these lines to match the 10 other times you have entered your COMPANY NAME by now:
authorId you have to find by opening up your newly created debug token bar file using a zip program and digging through the MANIFEST.MF file.
03-09-2012 08:18 PM
I was having this problem, and ryansweny's solution worked for me. But when I went back to the instructions i realized that I missed putting my debug token into the bbwp.properties file. After I did that it worked as well, even once I reverted the change in bbwp/AirAppTemplates/src/blackberry-tablet.xml
03-09-2012 08:33 PM
This. Adding the DebugToken to the bbwp.properties file solved the problem here. My guess is that it was packaging it without a debug token at all, considering that the size of my archive went up by 2k when i did that.
03-09-2012 08:37 PM