03-16-2011 02:41 PM
so has anyone successfully signed their application from flex builder and gotten the proper files in the .bar? Or is there a rim employee who can possibly look into this and make sure we are doing the steps correctly?
03-16-2011 03:41 PM
I have actually gotten the signing to work with the latest 0.9.4 on Windows 7 - I can't think of anything I'm doing differently.
Selected my .p12 cert I made back when I manually signed stuff, then just chose to export release build and my .bar files have 5 files (2 author, 2 rdk, 1 manifest) in the right folder. Seems to be working on both apps I've tried.
03-16-2011 05:21 PM
then i really wish there were some sort of documentation explaining exactly how to go through the signing process through flex (without command line). Because i made my certificate via flex.
03-16-2011 05:28 PM
@ahaz: they posted documentation on how to do it through burrito here:
not sure if u saw that already. i also recommend you order new keys in case it might have to do with some sort of corruption of the DB for the key.
03-16-2011 05:59 PM
I think there's just something wrong on the IDE side. I'm having the same trouble signing my .bar with 0.9.4 via the IDE. Even though I'm exporting a release build, if I manually take the .bar file and try to sign via the command line like I did in 0.9.3, it tells me I can't because the .bar is still in debug mode!
So even though we are explicitly trying to export a release build, adobe ain't giving it to us.
I saw another post you made JRab in another thread, I will try when I get home.
This whole process is very trying on the patience.
03-16-2011 06:20 PM
4. In the Proxy entries field, select the HTTP schema. Click Edit.
1. In the Host field, specify the proxy host address.
2. In the Port field, specify the proxy host port.
Im stuck on step 4, what proxy host address and port are they talking about?
03-16-2011 06:22 PM
@ahaz: you can skip the section on proxy servers if you dont use one. only for those with it.
03-16-2011 06:23 PM
Here is the answer.
If your computer connects to the Internet through a proxy server, you should configure Adobe® Flash® Builder to use your proxy server during the signing process to contact the RIM® Signing Authority.
03-16-2011 06:37 PM
Ok, I figured out how to get it to work correctly in Flash builder 4.0.1 (This might also work in Burrito, but ive never used it so I don't know). What I did differently was restarted Flash Builder (I had had it minimized for weeks previously). After that I went to window>preferences>FlashBuilder>InstalledFlexSdks
in order to make sure it was using the 0.9.4 SDK (and it had reverted to an older one so you will want to make sure to check this). What I did differently than the instructions from Blackberry said to do was I clicked project>Export Blackberry tablet os release build (this option suddenly showed up after I restarted Flash Builder). I went through the steps on that and I was successful. I checked my bar by making a copy of it and unzipping it and the Meta.inf file now contains AUTHOR.EC, AUTHOR.SF, MANIFEST, RDK.EC, and RDK.SF
It does work perfectly, I just had to restart Flash builder for some reason. (I also changed the version# of my app just in case it would make a difference)
I hope this helps somebody and if you have any questions about any of the steps I took feel free to ask!
03-16-2011 08:39 PM
I ended up going back to the command line to package and sign my app. I've wasted too much time on this for my sanity's sake. For what it's worth, I have both 0.9.3 and 0.9.4 hanging around (though I made sure my settings were pointing to 0.9.4). They must be conflicting somehow. Wish I could figure out how to uninstall 0.9.3, but I don't see it in Add/Remove programs.
Anyways, I did it the manual way and now it's signed and submitted!
I used a refresher course from this thread, look towards the bottom of the 1st post: