05-19-2011 09:28 AM - edited 05-19-2011 09:38 AM
First of all I want to say I'm able to install signed Flex apps and unsigned Webworks apps
on my Playbook. But when I try to push, via USB, a signed WebWorks apps I got
result::failure 500 META-INF/AUTHOR.SF: SHA-512-Digest-Manifest mismatch
I don't know what I'm doing wrong because the signing process work
perfectly. But as you can see they dont' fill the actual_dname,actual_id
and actual_version value. But when I check In the MANIFEST file I can
see the Application-Name,Application-Id and Application-Version value
and the good Package-Author,Package-Author-Id I give in the
blackberry-tablet.xml and config.xml.
Any help will be appreciated
Solved! Go to Solution.
05-19-2011 01:15 PM
Have you checked out the steps in the Developer's guide for signing WebWorks applications for Tablet OS?
It's a bit different than the signing process for AIR development on the PlayBook
05-19-2011 03:47 PM
But now I receive a "unable to register because there are no more attempts" error with
this command: "blackberry-signer -register -csjpin MYPIN -cskpass MYPWD "client-RDK-MYCLIENTNO.csj"
Should I have two key...one for my AIR apps and one for my WebWorks apps ?
Because when I use this command:
bbwp "C:\app\myApp.zip" -gcsk MYPWD -gp12 MYPWD -buildId 10 -o "C:\appcompil\output"
I got a "failed to find signing key "...wich signing key is talking about...i have a ".p12", ".db", ".csk",
and 2 ".csj" files (PBDT, RDK) ?
When you will have time can you plz work on a GUI signing tool. I think I talk for many "we" spend
toooo much time on signing apps. (Now I feel better).
05-24-2011 01:39 PM
1) Don't use Flash Builder Burrito to communicate with RIM authority. If he fail you will not receive any error message.
2) If in the registration form you enter upper case letter in your PIN (CSJ PIN) the system will automaticly lower the letter so be carefull when you use this command : blackberry-signer -register -csjpin 999A9999 etc..
06-02-2011 10:17 AM
one possible cause of your problem is that you may have performed the two signing steps in the wrong order. You need to ensure that you first sign with the RIM key and then self sign, not the other way around. If you do reverse the order of these steps you will get the error that you encountered.
06-02-2011 10:36 AM