Adobe AIR Development

[smiley]

fixed the publish error and now i'm getting this when signing

Response = Signature Response
Confirm = null
Error = Code signing request failed because Application-Development-Mode in Mani
fest is present and is not set to [false].
]

what is that?

[JRab]

i think the bar file you are trying to sign is still in debug mode. are you using an IDE or command line when you package your project?

[smiley]

---

JRab wrote:

i think the bar file you are trying to sign is still in debug mode. are you using an IDE or command line when you package your project?

---

I use the IDE and i specifically select Production and checked enable digital signing.

[tensioncore]

Did you follow the GUI instructions from the other guide thread??
If it keeps failing, the COMMAND interface for signing isn't that daunting, and besides I make note of all things you need to know so it should be pretty straightforward to accomplish without errors.

[smiley]

---

tensioncore wrote:
Did you follow the GUI instructions from the other guide thread??
If it keeps failing, the COMMAND interface for signing isn't that daunting, and besides I make note of all things you need to know so it should be pretty straightforward to accomplish without errors.

---

the gui instruction is easy and i tried and no errors reported.  I just want to make sure it works.

how do i verify that the .bar is in fact signed.  i checked the times and they are the same

Edit:

I tried signing from the cmd line and i got this error ms

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.

so i guess this means the app is signed

[peter9477]

@smiley, you can always extract the contents of your bar file (it's merely a .zip file with a different extension) and inspect the MANIFEST.MF file with any text editor.  That will let you troubleshoot such problems on your own.

[JRab]

i dont think the gui is actually working. it seems misleading at best. i did a sign via burrito and everything seemed to go well. but no email. i then did a signing via command line and it popped up an obvious errror that my version number was wrong. also i didnt use a blackberry-tablet.xml file in my project. and the gui didnt pick up on it at all.

so i recommend you do the command line and clear up any errors you find that way. the gui doesnt seem to be working from what i've seen.

[peter9477]

@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.

[tensioncore]

If everything is there then you shouldn't have any problems because that would indicate that the returned commands from RIMs servers were successful. Otherwise from my tests it doesn't modify anything if the signing process fails

[peter9477]

---

JRab wrote:

i dont think the gui is actually working. it seems misleading at best. i did a sign via burrito and everything seemed to go well. but no email.

---

"No email"?  I never got an email in response to my signing attempt, though it clearly succeeded.  

Are you supposed to get an email from RIM with each successful signing?  

The only email I got was the "registration request completed successfully for client XXXXX" message, from websigner .at-sign. ws-smtp.rim.net.