Hello,
Your deploy tool creates incorrect bar file for Blackberry Playbook( on Windows, with Marmalade SDK 6.0.2 ).
That bar file, can be signed and deployed on device, but it can't be verified. And that's why it can't be uploaded on Blackberry App World ( you get a message "Some files are missing signatures" )
The problem is in zip options, used by Marmalade deploy system.
Your tool need to create bar(zip) file and do not add directory entries.
For MacOs it will be something like "zip [b]-D[/b] -r ../bar_file filesToAdd"
Here link on same problem on blackberry forum:
http://supportforums.blackberry.com/t5/BlackBerry-App-World-General/Adding-release-Some-files-are-missing-signatures/m-p/1623471
You can check resulting file, using following command:
"%ProgramFiles%\Research In Motion\BlackBerry WebWorks SDK for TabletOS 2.2.0.5\bbwp\blackberry-tablet-sdk\bin\blackberry-signer.bat" -verify file_name.bar
Hello, I have a problem. Can`t build project for android after including s3eDialog.
Marmalade's BAR signing is FUBAR. I highly recommend creating unsigned BAR files with Marmalade, and then manually signing them with RIM's command line utilities. Something along the lines of:
blackberry-signer -verbose -cskpass YOURPASS -keystore sigtool.p12 -storepass YOURPASS YOURBAR.bar RDK
blackberry-signer -keystore sigtool.p12 -storepass YOURPASS YOURBAR.bar author
blackberry-signer -verify YOURBAR.bar
Yes, I create unsigned bar files with Marmalade, and then sign them manually. But Marmalade creates incorrect bar( which can't be verified after signing ), so I need to repack it manually ( using zip from MacOs with -D option ).
That's weird. I always verify with:
blackberry-signer -verify YOURBAR.bar
and it always comes back as verified, no issues at all. Perhaps this was broken in v6.0.x - I'm using v5.2.4 with manual signing and the verification step is fine.
Ok someone please tell me how to create unsigned bar files? Do you just Package without the Keystore File? If so, when I do that, I get an error when I run the RIM commands:
blackberry-signer -verbose -cskpass YOURPASS -keystore sigtool.p12 -storepass YOURPASS YOURBAR.bar RDK
blackberry-signer -keystore sigtool.p12 -storepass YOURPASS YOURBAR.bar author
blackberry-signer -verify YOURBAR.bar
How are you guys able to package a bar file and sign it correctly??
OK SO it seems that whatever Marmalade 6.0.x is doign to create the bar files.. it's doing it WRONG by including directory names as files.
I solved this by downloading GNU Zip (which also requires BZIP.dll). I packaged everything you need and you can get it here:
https://www.dropbox.com/sh/xem8msduyyff808/IEWbdaYrkQ
So here are the steps.
0) Open up that .zip file and place the ZIP app in a directory that is in your environment path. You need to be able to run this from anywhere!
1) Deploy your app via marmalade but don't let Marmalade sign it.
2) Once done click on the "explore" button which opens up that directory and then go to the intermediate_files sub-directory. In there do a shift+right-click and select "open command window here" option (VERY cool little feature)
3) Run this command:
zip -RD .bar *.*
4) RDK and Author sign it. Do a verify to ensure things are as they seem.
5) upload to RIM Vendor Portal
6) ???
7) Profit!
Solution posted here: https://www.madewithmarmalade.com/devnet/forum/playbook-submission-builds