Adobe AIR Development

[peter9477]

---

tensioncore wrote:

PLEASE NOTE: you must copy these exactly except for where I TYPED IN CAPS - these you change to your hearts content, otherwise the rest of the commands NEED to be there, such as the word "author" and "RDK" etc.

---

You might want to edit that to state explicitly that both the text in ALL-CAPS and the angle brackets should be replaced by the relevant text, or some may leave the angle brackets in, to possibly disastrous effect.

[tensioncore]

thanks, edited!

[Acenet]

Short question about First step:

blackberry-signer -csksetup -cskpass -storepass <password>

Is param -storepass needed or not ?

In the official page it's not, but I didn't catch any update on this command in this post...

[eugenevk]

I get an error when executing the first step of the signing process. I entered the following at the command prompt (with appropriate values filled in):

blackberry-signer -verbose -cskpass <my_CSK_password> -keystore <my_p12_file> -storepass <my_p12_file_password> <my_BAR_file.bar> RDK

and then get the following error:

...
41 43 38 55 57 38 58 33 7a 6b 56 61 59 32 75 31
2f 47 70 4f 4f 44 37 7a 43 48 36 36 30 41 3d 3d
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 Entry-Point-Type value is not recognized.
]
barsigner error: server error: Code signing request failed because Entry-Point-Type value is not recognized.

I have created the BAR file with Flash Builder (F11 key) and it's an AIR application.

Anyone any idea?

[peter9477]

The Entry-Point-Type is found in your MANIFEST.MF file, inside the .bar. What does yours say?

[eugenevk]

Entry-Point-Type: Qnx/AirDebug

[peter9477]

That means you compiled/built with debug mode enabled.  

I think previously we heard from people who'd done that but who had not received that error message.  Perhaps RIM has updated the server-side code to check this and reject signing attempts for debug-mode apps though, which makes sense.

Anyway, it should read just "Qnx/Air" when you've got it fixed.  Read back or in other threads to learn how to disable debug mode properly, if you don't know how.

[peter9477]

I was partly wrong: others have seen the same error before so this isn't a recent server-side change.

[eugenevk]

Thanks Peter, you were 100% right. I should have used Ctrl-F11 instead of F11 in Flash Builder. However, now I get the following error:

...
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 Application-Development-Mode in Manifest is present and is not set to [false].
]
barsigner error: server error: Code signing request failed because Application-Development-Mode in Manifest is present and is not set to [false].

I checked settings in FB:

and even FB gives me the same error, while I do have selection 'Production mode' as you can see in the screenshot.

The error:

In the manifest file, the Development mode is set to true instead of false.

[peter9477]

Please try searching.  In this thread or another related to signing we've already seen exactly the same error and some sort of resolution (which may have been to resort to using the command line... I don't recall and don't really follow anything to do with Flash Builder).