11-19-2012 09:28 AM
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.
11-19-2012 12:18 PM
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?
Note: at this time, the first one is not working- server error
11-19-2012 01:45 PM
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.
You can use either form, they'll both provide the same keys.
11-19-2012 01:52 PM
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:
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.
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.
11-19-2012 02:27 PM
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
11-19-2012 03:42 PM
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.
11-19-2012 08:29 PM
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.
11-20-2012 01:48 PM
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.
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
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