04-11-2011 03:55 AM
First, thanks for this post, great job!
But still I have a problem. I follow all your step with success and send myapp.bar to RIM who approve it. But they say that my .BAR is not signed by :
Item(s) that need attention: - The application is not signed
I the last step I have "bar signed." And it's work on the simulator.
Do I have a way to try if my .BAR is well signed?
Thanks in advance
04-11-2011 07:24 AM
04-11-2011 07:57 AM
Hi, and thanks for this answer
I have this :
MyApp.bar -- air Folder -- myapp.swf -- ... -- META-INF Folder -- AUTHOR.EC -- AUTHOR.SF -- MANIFEST.MF
It's in META-INF folder that I need 5 files? Do you know what I have miss?
04-11-2011 10:43 AM
04-11-2011 10:18 PM - edited 04-11-2011 10:19 PM
I was able to create the initial bar file but that is where I get stuck.
I tried the following command:
"C:/PATH/Adobe Flash Builder Burrito/sdks/blackberry-tablet-sdk-0.9.3/bin/"blac
kberry-signer -verbose -cskpass "mypassword123" -keystore "C:/PATH/Adobe Flash Builder Burrito/sdks/blackberry-tablet-sdk-0.9.3/bin/outpu t_file.p12" -storepass "mypassword123" MyApp.bar RDK
And I get the following Error:
barsigner error: keystone: C:/PATH/Adobe Flash Builder Burrito/sdks/blackberry-tablet-sdk-0.9.3/bin/outpu
t_file.p12 (The system cannot find the file specified)
If I create a dummy p12 file and rerun the command, I get a different error.
What am I missing? How can I run this command successfuly?
04-11-2011 10:43 PM
did you create a p12 file using the command line before?
04-11-2011 10:49 PM
I didn't realize that the original post was not a complete account of how to package and sign an app. I am creating the p12 file now, but am running into other errors. I will try to see if I can fix it myself.
One question: Do you need to increment the version everytime you unsuccessfully package and sign your app -- or do you just need to increment the version after you submit the app to app world?
04-11-2011 10:51 PM
yes, every time the signing fails / succeed you will need to increment the version on the next signing. (e.g. 1.0.0 > 1.0.1)