Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
03-16-2011 08:46 PM
03-16-2011 08:49 PM
FYI - I requested a new CSJ file, and did the create and register process through the FLash Builder IDE, and signing is working fine for me now.
03-16-2011 09:18 PM
Actually, nevermind. It only worked fine the first time (when I used 'create' and 'register' ). Subsequent attempts are not signing. I think RIM could have at least put in some basic error handling in, to see whether code signing was successful or not. I bet they will get a few .bar files from people who think they have signed but really have not.
I will stick to signing from command line for now.
03-16-2011 09:44 PM - edited 03-16-2011 09:44 PM
UGH last post from me now I promise. The reason the IDE was not signing my .bar on subsuquent attempts was that I forgot to change the version number of my app. So it was getting an error but was silently failing. It works when I change the version number.
03-17-2011 10:40 PM
Just wanted to add my confirmation that "YES", it does work via Flash Builder Burrito using 0.9.4 to sign the app.
The major caveat is that you add
to the compiler settings (after -locale en_US)
and then do a "clean" of the project.
FB states that it does nothing when compiling the swf, but apparently it *does* as it actually signs the app when you do it that way It states that all debug information has been removed if you try to run it in debug mode.
Once you do this, and do an "export release build", you should get a nice bar file with multiple files in your meta-inf folder.
03-17-2011 11:15 PM
then i really dont understand what i am doing wrong. Ive done everything that each person says has helped them to properly sign (including getting new keys and creating a new certificate) but i have yet to have any luck signing.
03-17-2011 11:16 PM
I know it's a bit of a pain, but can you post the steps you are following to perform your export (or point to the post in this thread where you did that)? We might be able to figure out where the sticking point is.
03-17-2011 11:26 PM
added:-debug=false to compiler args
went to project > clean project
project > export release build
Chose export and sign > next
Put check in include Blackberry tablet os libraries in build path, and in enable digital signing
end result is with a bar file unsigned and a <MyApp>.bar.sig file that is empty in the same folder as the .bar
03-17-2011 11:32 PM
Did you also add the blackberry-tablet.xml file (same directory as your MyApp.xml file)?
<qnx> <initialWindow> <systemChrome>none</systemChrome> <transparent>false</transparent> </initialWindow> <publisher>hsharma.com</publisher> <category>core.games</category> <icon> <image>Icon_86.png</image> </icon> <splashscreen>crazygems-splash.jpg</splashscreen> </qnx>
making changes where necessary (you can remove the splash screen and if you've added your own images to the MyApp.xml, you don't have to worry about the "icon > image" node either.
Very important piece to this file is the publisher node. That's the thing that needs to match up to whatever name you signed your keys with (company name or individual name). This must match that exactly.
Make sure this xml file is included in the files that are used during the signing process.
03-17-2011 11:33 PM - edited 03-17-2011 11:34 PM
Did you try export blackberry tablet os release build instead of export release build? That is what worked for me. If you don't have that option shown under project try restarting flash builder and make sure it is set to use 0.9.4. That is what worked for me as I wrote in a post on page 2 or 3 here. Also, I didn't put debug=false and it still worked fine.