03-18-2011 05:13 PM
When I follow these steps exactly (which is what I was doing before anyway), and when I unzip my bar file that is created, I only have one file in the manifest folder. Does this mean it is not signed? If so, why is that happening?
03-18-2011 05:16 PM
03-18-2011 07:52 PM
I found that the Flash Builder signing fails silently. Where you would see an error message in the command line, no error appears in Flash Builder, leading to beleive it was successful, when upon checking the .BAR, it really wasn't.
For me, I was forgetting to update the version number in the -app.xml file. You need to update the version number on each signing attempt. So if you haven't done so, try upgrading your version number, and also double check your company name. After updating the verison number, I can sign the app from FB Burrito.
03-19-2011 05:38 AM
Could you please tell me, which files should be there if the bar is signed?
I'm getting kind of nervous, because I just updated my three apps with manual signing and the process gave me a positive feedback on all files. But I just had a look into the archives and there is only one entry every META-INF folder...
03-20-2011 11:41 AM
Check out the MANIFEST.MF file and check to see whether it mentions anything about "test" in the dname property. Also check to see if there is a publisher name in there.
If you see "test" or somethinng about "development=true" in the MANIFEST.MF file, then the swf that is being exported is not the "release bulid". Try adding -debug=false to the compile options. This will guarantee that it's the release build.
If you do not see a publisher name, make sure you have a "blackberry-tablet.xml" file. This is where you put your publisher name. This should match exactly whatever company or individual name you used to sign up for your signing keys.
I put a reference in the "signing" sticky at the top of this forum (http://supportforums.blackberry.com/t5/Tablet-OS-S
03-20-2011 08:43 PM
As Comantis said, this is VERY important: "You need to update the version number on each signing attempt."
You can only sign the app with the signing authority ONCE PER VERSION NUMBER. If you're having problems with the BAR not being signed, it's probably because you need to increase your version number.
03-24-2011 07:32 PM
In addition to incrementing versionNumber with every build, I've discovered another VERY IMPORTANT step that was undocumented and will silently stop your build from being signed. You must set your "copyright" tag to be exactly your vendor name. If it's anything else, your app will not be signed.
I've documented it in more detail here: http://supportforums.blackberry.com/t5/Tablet-OS-S