Adobe AIR Development

[tensioncore]

@JRab thanks for clarifying the GUI method because I haven't tested it and burrito is beta technically so I would have to second your statement...since RIM published their SDKs on their own and commands from their utilities I would say you can trust out of the box especially when those of us who use the COMMAND are getting clear and un-deny-able results..

[JRab]

hey peter,

yes, if this is in like the Java code keys, they are supposed to email you stating that you signed the app. its supposed to be some sort of security measure rim has to notify that an app has been signed using your credentials. also i believe tensioncore stated he received an email after he signed his. im not sure if he meant after he registered or after he signed.

[smiley]

---

peter9477 wrote:

@smiley, my post just above this was in response to your first request about the debug mode still being enabled.  

Same answer applies to the question of "is it really signed", but this time you can simply inspect the META-INF folder to see whether it contains more than just the MANIFEST.MF file.  If it has the AUTHOR.EC/SF and RDK.EC/SF (that's four files, two extensions for each base name), then it's signed.

---

peter9477.  I dont see any of the files UTHOR.EC/SF and RDK.EC/SF in the bar file.

here is the struct of the .bar file

..

air

META-INF

in META-INF folder it has

MANIFEST.MF

[peter9477]

Then it's definitely not signed.  The first signing stage (second last step in tensioncore's HOW-TO) will update the manifest.mf file and insert the rdk.* files, while the final stage will insert the two author.* files.

[JRab]

@smiley: yah looks like that means its not really signing via the GUI. stick to the command line packaging and deploying and signing. the export never worked via FB4 im not surprised this is failing too.

[tensioncore]

@smiliey - your app has NOT been signed successfully

@JRab - I got an email confirming that my app was successfully signed against RIMs server

[JRab]

@tensioncore: thanks for confirming this! its a sure-fied way to know if your app was successfully signed.

[smiley]

argg!! here is what i'm doing

1 build the app in FB

2 in DOS cmd do the package

3 run step 1 to sign but it then tells the bar file is already signed

Connecting to url http://www.rim.net/Websigner/servlet/RDK-Waterloo
Sending properties to server...
Properties of response := [
Version = 1
Response = Signature Response
Confirm = null
Error = Code signing request failed because this file has been previously signed
.
]
barsigner error: server error: Code signing request failed because this file has
 been previously signed.

[peter9477]

---

tensioncore wrote:
@JRab - I got an email confirming that my app was successfully signed against RIMs server

---

@tensioncore, could you or anyone else who's got one of those emails please post some information (probably not in spam-harvestable form) about what address or server it is being sent from?  Also, any idea how quickly it arrives?  More or less instantly, or after 5-10 minutes, or ?

I've checked my mail server logs carefully, and see no sign that anyone is even attempting to send me email when I sign.  I've successfully signed two versions of my app now as a test.

[elena_laskavaia]

Just to answer few question on this thread:

1) Gui signing does not work because of the bug, you have to sign it via command line using posted docs. Means you cannot use "Export" in this release in FB 4.5.

2) If you receive an error that package is already signed means you signed an application with the given name and given version. Contents does not matter. You have to change version. You can change 3 digit version using adobe xml file. Or you can change 4th digit via command line giving -buildId <number> to blackberry-aripackager

3) blackberry-aripackager can also call signing tools if you provide -signRim -signDev and all storage and key passoword options (see command line help)