Adobe AIR Development

[brentcameron]

Thanks Mark.  I saw the documentation fix this am... you might want to put that in bold until they fix the program.  

[streak81]

---

elena_laskavaia wrote:

I don't understand what do you mean it is not there,it is by default when you launch, unless you do an export release

---

Hi Elena,

I know there USED to be a setting to choose development or production mode.  This is what I get now:

[MSohm]

It is no longer a manual setting.

When doing a Run As or Debug as, the application should always be built using debug mode.

If you perform an Export -> Release build the application should always be built using release mode.

[dbigham]

I've spent the last 2-3 hours trying to get an unsigned application deployed to my PlayBook, but without any luck, because of the BarFileUnsignedError issue.

First of all, I would recommend changing the page here:

http://docs.blackberry.com/en/developers/deliverables/23959/Create_a_debug_token_cmd_line_1585437_11...

... to more prominently link to:

http://docs.blackberry.com/en/developers/deliverables/23959/Configure_app_for_debug_tokens_cmd_line_...

It should be either a main heading on the former page, or a main bullet point, not a link at the end of a paragraph.

Here's what I've done:

- Successfully installed the debug token on my PlayBook.

- Edited by blackberry-tablet.xml to include:

  <author>Daniel Bigham</author>

  <authorId>...</authorId>

- Verified that the value I used for authorId matches the value in MANIFEST.MF of my debug token BAR file under Package-Author-Id.

- Then I run:

blackberry-airpackager -devMode -package BabyNames.bar -installApp -launchApp BabyNames-app.xml BabyNames.swf blackberry-tablet-icon.png screen.png -device 192.168.1.106 -password ...

... and I get:

result::failure 500 BarFileUnsignedError

Maddening.

[MSohm]

Did you successfully deploy the debug token bar file first? Does the debug token show up under Options, Security, Development Mode.

Did you place the device into Development Mode first?

[dbigham]

I thought I had replied to this already but I guess not.

- Yes, the debug toekn bar file was successfully deployed first. It is showing up properly under Options, Security, Development Mode.

- Yes, the device is in development mode.

[elena_laskavaia]

Are you using sdk 1.0.1?

run

blackberry-airpackager -listManifest <debugtoken>.bar

blackberry-airpackager -listManifest <youapp>.bar

and compare Authod-Id and Author tags

[dbigham]

Yes, I am using SDK 1.0.1.

I suppose I should have clarified that my app BAR file reports that it is using a Package-Author-Id which has the "test" prefix. ie. It's not using the Author-Id of the debug token BAR, and so the error I'm getting is in a sense expected.

So a more specific question is why my app BAR file is being signed with a "test" Package-Author-Id desipite following the instructions exactly.

For reference sake, here's the command I'm using to build the BAR:

blackberry-airpackager -devMode -package BabyNames.bar -installApp -launchApp BabyNames-app.xml BabyNames.swf blackberry-tablet-icon.png screen.png -device 192.168.1.106 -password ...

[JRab]

@dbigham: Sounds like your blackberry-tablet.xml isnt setup properly or isnt being read by the packager the right way. can you copy and paste the contents of your blackberry-tablet.xml file? thanks.

[dbigham]

<qnx>

  <initialWindow>

    <systemChrome>none</systemChrome>

    <transparent>true</transparent>

  </initialWindow>

  <publisher>Daniel Bigham</publisher>

  <author>Daniel Bigham</author>

  <authorId>gYAAgByrhWKIB9FA9ofsm-0DzLI</authorId>

  <category>core.internet</category>

  <icon>

  <image>blackberry-tablet-icon.png</image>

  </icon>

</qnx>

<qnx>