01-06-2013 02:33 PM
Hi! First post here
After building and packaging with QtCreator even with Release Build selected, blackberry-signer complains with a
Code signing request failed because Application-Development-Mode in Manifest is present and is not set to [false].
What do I need to do to get over this problem?
Solved! Go to Solution.
01-10-2013 03:47 AM - edited 01-10-2013 04:10 AM
I have the same problem You can only unzip the bar file, modify the MANIFEST.MF file, set Application-Development-Mode to false and zip the files back into a bar file. But I don't know if this is the best solution. After I sign the bar file using blackberry-signer command, I run blackberry-signer -verify app.bar and it shows an error:
Error: Some files are missing signatures
I'm doing something wrong or this is supposed to happen?
LE: I want to mentiont that I double checked the .SF files from the META-INF directory and it seems that all my files are signed. I also installed the signed bar on the simulator and it works. So, my question is: can I submit the app as it this, even if the -verify command gives me that error?
01-10-2013 05:20 AM
01-10-2013 05:31 AM
Hmmm, I didn't thought about using nativepackager. You're right, using blackberry-nativepackager works and it won't give any errors when executing blackberry-signer -verify.
Thanks for the tip!
01-10-2013 05:35 AM
I'm using Qt Creator 2.6.1.
Here's what works for me:
Perform "Clean all", then "Device - Release Build". Do not run application after this as this will produce debug BAR file.
After building, package the BAR file manually. You can find my packaging script in this thread:
Put this script into application folder, ensure all other paths and passwords are correct and the buildId.txt exists.
After running it you should get a signed bar which passes validation.
Note that version number (build number) will be automatically incremented every time you run the script.
You'll need to create buildId.txt and put '1' into it when running the script for first time.