04-04-2013 06:18 PM
Since then I have changed my signing key in eclipse, "run as" reports an error:
result::failure 881 application author does not match debug token author
Yes, in the MANIFEST.MF file in the BAR package still has the wrong (old) author. But in the bar-descriptor.xml is the correct (new) author.
When I run blackberry-nativepackager and blackberry-deploy on the console, then it works.
How does "run as" build a BAR package in eclipse ? And how can I fix it?
Solved! Go to Solution.
04-05-2013 10:34 AM
It could be installing an old bar file. Try to do a Clean, delete the bar file from the project and rebuild.
04-05-2013 01:46 PM
Do you mean in eclipse "Clean Project" (this execute rm -rf arm arm-p x86, delete the entire dir), yes I did that and there is no old BAR package file in my project but it did not help.
I delete the project in my eclipse and imported again, but it did not help.
I create a new project with "new" -> "Black Berry Project" -> "Cascade Application" in my eclipse workspace. I change nothing in this project and build a BAR package but it did not help.
It is still my wrong old Package-Author in MANIFEST.MF file but in "Window" -> "Preferences" -> "BlackBerry" -> "Signing" is my new "Author" name and in
But when I build an BAR package for the simulator, Package-Author is the author name from bar-descriptor.xml.
How does eclipse build the BAR package ? Check eclipse some properties from my Dev Alpha Device? But there is my new debugtoken with the new author installed ?
04-05-2013 03:35 PM
In the BlackBerry Native SDK to go Window -> Preferences -> BlackBerry -> Signing and remove all debug tokens created with your old keys. The SDK looks there for that information when deploying to a device and will use the first debug token it finds. It looks like it's picking up a debug token from your previous set of code signing keys.
04-10-2013 05:12 PM
In the BlackBerry Native SDK to go Window -> Preferences -> BlackBerry -> Signing and remove all debug tokens created with your old keys.
I removed everything, including the new debug token and create a new one.
Thanks for your help.