04-11-2011 12:46 PM - edited 04-11-2011 12:56 PM
My app was recently rejected b/c it was not signed but I could have sworn I did sign it. I followed all the directions on this page: (http://docs.blackberry.com/en/developers/deliverab
I'm new to this so I'm sure I missed something, but I am unsure what it could be. I checked everything and eveything seems to be in order. So then I tried to start from scratch and reset my certificate info in flash builder, but when I tried to re-register the RIM certificate, it tells me that I can only register once.
So I've requested a different RIM certificate. (Though, Is it better to ask RIM (especially in terms of the free playbook offer) to be able to register this certificate again? If so, how is this done?)
In any case, it looks like I had signed the certificate the 1st time. What could of gone wrong?
04-11-2011 12:57 PM
Apps have to be double-signed. Its easy to miss the second step. Change the .BAR to a .ZIP, then use your fav zip prog to look in the META-INF dir. There should be 5 files. If not, its not signed properly.
You can only register the code-signing keys once, but once they are registered you can sign as many apps as you want. You shouldn't need new keys unless you have deleted the files or something. Just re-execute the last two commands to sign new file.
You can't sign the same VERSION however more than once. You have to build a new version with a different version number in order to sign the file again.
04-11-2011 01:01 PM - edited 04-11-2011 01:02 PM
It is a really good habit to have a check list of things that need to be done with each new release. It's the little things that can mess things up. I have a WORD document that I check off each time I want to promote a new product or version. Things like:
04-11-2011 01:07 PM
There aren't 5 files in the META-INF folder, so it appears I didn't sign it, but I am still dumbfounded as to why not.
What do you mean by double signing? Is the process specified on the following page? If so, I could have sworn I followed every step.
04-11-2011 01:21 PM
04-11-2011 01:28 PM
The first step adds 3 files. The 2nd step adds 2 more. The steps are outlined in the same doc further down when it talkes about signing by command line.
Apparently, FlashBuilder isn't (or didn't) completely sign the app. I think I read somewhere that .93 only did one step of the signing, but .94 fixes it. Having said that, I haven't tested to make sure this is the case and I only have a somewhat vague recollection to go on anyway. Bottom line is that you may have followed the steps in the doc, but I can't say for sure that FB is doing the right thing or not.
Hopefully you can do some testing and then we will know for sure. Make sure that you are using the latest SDK.
04-11-2011 01:47 PM
I have the latest Blackberry Tablet OS SDK (0.9.4).
I'm not really a command-like kind of guy, but perhaps I have no choice. Hopefully I can avoid it.
Has anyone submitted their app successfully and compiled it using flash Builder - not by command line? If so, any thoughts on my situation?
04-11-2011 02:22 PM
The command line is incredibly simple once you get it set up. Trust me, it looks extremely intimidating but is actually quite manageable. However, if you have already set up your .p12 file through Flash Builder, you will need to set up new keys to register them via cmd line.