Adobe AIR Development

[DachFlach]

I only just got a PlayBook the day before last.

Previously I was using the Simulator.

It seems to be an issue with using a Signed Bar on the device itself.

I ran out of time today but will put more effort into another try on the weekend.

I will report back.

[UberschallSamsara]

If you're iterating on debug and testing on a real device, you probably want to be using a debug token.

And as per comments in the other thread, the SWF needs to have been compiled with debug options

for the debugger to be able to hook into it.

[DachFlach]

So, the answer to my problem is:

Do not try and debug a Signed Bar on an actual Device?

[UberschallSamsara]

Not necessarily, it's just that if you are debugging, you are likely iterating on edits/rebuilds/reinstalls.

If you're using a debug token you cut some time out of your iterations by not having to send data

back and forth to RIM signing servers for intermediate debug builds that don't really need to be signed.

Edit:  Now that I think of it, I don't recall if you can sign a debuggable .bar, so maybe the answer is yes

you need to go the debug token route.  I've never tried to sign a debug build, at least not intentionally.

[DachFlach]

Okay, well this brings me to an earlier issue I had.

Debug token errors, previously signed or or something like that.

I cannot look into it further tonight but want to thank you for your effort this time and previously with my Simulator issue.

I will report back sometime over the weekend ( hopefully ).

[DachFlach]

I am likely missing something obvious, so thank yu in advance for your patience.

Followign instruction from ehere: http://developer.blackberry.com/android/documentation/configure_app_signing_2007101_11.html

I get this error:

Not yet registered to request debug tokens.

However, I try use the -debugtokentrequest, I get this error:

Unable to register client because there are no more registration attemopts...

Does that not mean that I am registered already?

I am able to sign apps via the Graphical Aid..  I just cannot register a debug token via commandline.

[UberschallSamsara]

Do you recall whether you registered both the RDK and the PBDT CSJ files, or did you maybe register just the RDK file?

[DachFlach]

Using this command:  blackberry-debugtokenrequest -register -csjpin XXX -storepass XXX client-PBDT-1919755.csj

I receive this error:

Unable to register client because there are no more registration attempts...

Do you think that means that the PBDT is already registered?

Or could it mean something else?

I am able to sign a bar, so I assume that means that the RDK is registerd fine.

[DachFlach]

I feel like I am going in circles here.

Using the advice from here: http://supportforums.blackberry.com/t5/Adobe-AIR-Development/Compile-and-Debug-without-Flash-Builder...

blackberry-airpackager -target bar-debug -connect [YOUR COMPUTER'S IP ADDRESS] -package HelloWorld.bar -installApp -launchApp HelloWorld-app.xml HelloWorld.swf [ICON FILE NAME] -device [PLAYBOOK IP ADDRESS] -password [SIMULATOR PASSWORD]

If I use that I get this error:

Failure 881 required signatures missing <RDK,AUTHOR>

I do not want to sign it, I want to debug it. Should that command work or is that old and missing something?

[UberschallSamsara]

That article is from 2010.  Note that the commandline debug instructions currently posted at the AIR dev micro-site

include an argument for specifying the debug token:

"When you package your application, include -debugToken to extract author and authorIdfrom <token> and apply it to your application.

blackberry-airpackager -devMode -debugToken <token> -package <Project_name.bar>
<Project_name-app.xml> <bar-descriptor.xml> Project_name.swf <ANE_files.ane> <others files...>

"

However since it sounds like you're not able to generate a debug token right now, you probably don't have

one to pass on the commandline.  (I'm not quite sure why you can't generate debug tokens; it's starting

to sound like something wasn't done right when you set up signing, but since all of the signing instructions

I've seen are very cook book-ish and don't really explain in depth the role of each file and each step, I'm not

sure how to proceed w/resolving the issue.)