Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® World™ Development

Reply
Highlighted
Visitor
Posts: 1
Registered: ‎10-31-2012
My Device: Playbook
My Carrier: BASE

signing problems

[ Edited ]

Hello, I have a problem by signing my application. I use marmalade-sdk-6.1.1-326649 and have signed my application with "blackberry-signer.bat -storepass mypasswd myapp"

But if I check my application with "signer.bat -verify appname", then I got Error: "Some files are missing signatures."

 

After my research and experiments I found what I should do to get right signed application:

1) extract .bar file into temporary directory

2) remove (if you have) all .ec and .sf file from META-INF

3) remove from manifest.mf all existing signatures, all string with

Archive-Asset-Name: xxx

Archive-Asset-SHA-512-Digest: xxx

4) add .elf-extensions to your binary file (rename to xxx.elf, by me this file was without extensions)

5) add .elf extensions in manifest.mf in the string Entry-Point: app/native/xxx.elf

6) add .elf extensions in blackberry-tablet.xml in the string <filename>xxx.elf</filename>

7) repack your zip with 7z

"7z.exe" a -tzip appname *.* -r"

8) sign your application with

"blackberry-signer.bat -storepass mypasswd myapp"

9)  check your application with "signer.bat -verify appname",

 

Only after 8 this steps I got rigth signed application !!!

It looked that .bar create or signing tools in marmalade-sdk-6.1.1-326649 are buggy.

Please fix all this tools ...

 

regards,