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

Web and WebWorks Development

Reply
Contributor
mobistar
Posts: 11
Registered: ‎12-27-2010
My Device: Not Specified

Error: failed to install debug token on Playbook

 

My attempts to install Debug Token on real Playbook device are failing with following error

 

 

Sending Install Debug Token request...

Info: Action: Install Debug Token

Info: File size: 100

Error: failed to install debug token

 

 

I am using following command from Blackberry WebWorks Tablet OS SDK 2.0.0.4 after I have put the Playbook I in "Waiting for debug token upload" mode.

 

 

blackberry-deploy -installDebugToken <path to debug token> -device <IP address of tablet>    -password <tablet password>
I know that the deploy command is reaching the Playbook because this same command fails with following error when I deliberatly provide incorrect tablet password. It also confirms that I am providing the correct IP address.
"Error: Authentication failed. There have been 2 of 5 failed attempts."
I am able to package and sign the bar file successfully so I know my environment is setup properly with the signing keys.
Now the only parameter that could be wrong in this command is path to the debug token. This parameter is pointing to client-PBDT-xxxxxxx.csj file received from Blackberry .
Can someone guide me on what else I can try to run my App on a real Playbook device. If I have a properly signed bar file, how can I load it on to the playbook ??
Can it only be done after having the Debug Token installed ??

 

 

 

 

Please use plain text.
Contributor
mobistar
Posts: 11
Registered: ‎12-27-2010
My Device: Not Specified

Re: Error: failed to install debug token on Playbook

FYI

 

I am able to install the signed app on the Playbook ? 

But I am still not able to install the Debug Token on the playbook.

Please use plain text.
Developer
Rhino1272
Posts: 47
Registered: ‎04-26-2011
My Device: Curve 2 8530 and PlayBook (soon)

Re: Error: failed to install debug token on Playbook

Are you using the default tablet password for the playbook 2.0 SDK which I believe is "playbook"?



My Blog: DevGuy.org
My Apps: Dive Planner
1. Please give Kudos by clicking the Kudos star kudos star below the post that helped you..
2. Please resolve your thread by marking the post "Solution?" that solved your issue.

Please use plain text.
Contributor
mobistar
Posts: 11
Registered: ‎12-27-2010
My Device: Not Specified

Re: Error: failed to install debug token on Playbook

No, its my own password.

Please use plain text.
Developer
Heiko
Posts: 125
Registered: ‎01-17-2011
My Device: Playbook

Re: Error: failed to install debug token on Playbook

[ Edited ]

Same problem here.

 

The (debug) signed bar file deploys fine to my Playbook, but the Debug Token fails to install.

 

I checked and there is a *.db file in my user directory.

I had also copied it elsewhere (with no spaces in path) and tried again - with no success.

Get "Error: failed to install debug token .."

 

Note that I only got the bar file to deploy once I plugged in the USB cable.

 

Wifi connection enabled throughout - and I use the Wifi network address I get when enabling Developer mode.

 

I also tried to click on load debug token button in security tab, but I stil fail to upload token.

 

Any other suggestions ?

 

.H

Please use plain text.
Developer
Heiko
Posts: 125
Registered: ‎01-17-2011
My Device: Playbook

Re: Error: failed to install debug token on Playbook

Never mind - stupid mistake !

 

Somehow specified my applicationname.bar filename as output for my debug tokenrequest.

Then found barsigner.db in my user documents dir and used it as debug token.

 

so new request had debug token as output:

 

 

blackberry-debugtokenrequest -cskpass ????? -keystore sigtool.p12 -storepass ????? -deviceId 0x????? D:\Projects\PB\debugToken.bar

 

Must have still been half asleep this morning :smileywink:

 

 

 

 

 

Please use plain text.