Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Adobe AIR Development

Reply
BlackBerry Development Advisor
MSohm
Posts: 14,649
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook

Re: Debugging from Graphical AIR OR command line

The error you are getting when trying to create debug tokens indicates that you didn't register the PBDT CSJ file.  Note that you need to install both CSJ files (RDK and PBDT).

 

Debugging is on release/signed BARs is not supported.  You need to use an unsigned BAR file with a debug token to debug.  Debugging features are disabled on signed BAR files.

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

I was going to order new keys and start from scratch. Is there a limit ot keys? This will be my third time.

 

Which of these two pages Should I be using?

 

http://developer.blackberry.com/android/signingkey/index/

 

https://www.blackberry.com/SignedKeys/codesigning.html

 

Note: at this time, the first one is not working- server error

 

 

Please use plain text.
BlackBerry Development Advisor
MSohm
Posts: 14,649
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook

Re: Debugging from Graphical AIR OR command line

There is no limit on the number of keys you can order, but keep this in mind if you already have applications up for sale.

 

Application Upgrade Appears as a New Separate Application

 

You can use either form, they'll both provide the same keys.

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

I have ordered new keys, successfully registered them, created a debug token, installed it and then followed these instructions to package and deploy to the device:

https://developer.blackberry.com/air/documentation/bb10/testing_your_application_cmd_ms_2010851_11.h...

 

When you package your application, include -debugToken to extract author and authorId from <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...>

 

This seemed to have gone well. Package created.

 

Next step:

 

blackberry-airpackager -target bar-debug -connect [Computer_IP_address] -package [project_name].bar -installApp -launchApp
[project_name]-app.xml [project_name].swf [ANE files][icon file][other_project_files]
-device [Simulator_IP_address] -password password

 

Now the error I get here is:

failure 881 required signatures missing <RDK, AUTHOR>

 

Was not step 1 supposed to extract this information from the debug token?

 

Is there any mistakes in that step? Assuming of course I have all the correct information entered on this side.

 

 

 

 

Please use plain text.
BlackBerry Development Advisor
MSohm
Posts: 14,649
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook

Re: Debugging from Graphical AIR OR command line

That step extracts the information from the debug token, but there is another step to sign it.  Run this command:

 

blackberry-signer -storepass <KeystorePassword> <BAR_file.bar>

 

You can read more about this here:  Sign your application using the command line

 

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

You mentioned I was to use an Unsigned Bar  when debugging.

 

Please use plain text.
BlackBerry Development Advisor
MSohm
Posts: 14,649
Registered: ‎07-09-2008
My Device: BlackBerry Z30, BlackBerry PlayBook

Re: Debugging from Graphical AIR OR command line

Right, sorry.  On your device go to Settings, Security and Privacy, Development Mode and check the debug token status. Does it say installed/valid or invalid?

 

Typically this error occurs if you don't have a debug token installed.

Mark Sohm
BlackBerry Development Advisor

Please refrain from posting new questions in solved threads.
Problem solved? Click the Accept As Solution button.
Found a bug? Report it using Issue Tracker
Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

Installed and valid.

Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

Is there any chance that there is a limitation in cname length during any of the processes?

My cname is 34 characters long and only displays 31 on the PlayBook itself in the development mode screen.

I don't want to change things now on a whim.

Please use plain text.
Developer
DachFlach
Posts: 148
Registered: ‎12-06-2010
My Device: Not Specified

Re: Debugging from Graphical AIR OR command line

Still plugging away at this.

Perhaps got a little closer.

 

 

I get two versions in the docs as to how to install the debug version of the app to the device.

 

This version:

blackberry-airpackager -target bar-debug -connect xxx.xxx.xxx.xxx -package SomeApp.bar -installApp -launchApp SomeApp-app.xml SomeApp.swf AppIconsForPublish -device xxx.xxx.x.x -password xxx

 

results in an 881 error

 

 

This version:

blackberry-airpackager -devMode -debugToken debug.bar -connect xxx.xxx.xxx.xxx -package SomeApp.bar -installApp -launchApp SomeApp-app.xml SomeApp.swf AppIconsForPublish -device xxx.xxx.x.x -password xxx

 

results in :   Error requesting application capabilities from the authorization manager: Exec format error

Please use plain text.