PlayBook Debug token invalid

Similar Questions

• Debug the invalid token (date OK)

  Hello

  I'm trying to get my debug token to work.

  I created & installed my token in accordance with the instructions provided in this article. However, on my PlayBook, debugging token appears as invalid (' Valid: No. ").

  I checked the date on my PC and my PlayBook (I even tried the PlayBook setting a few days in advance): they are both OK. Also, I used blackberry-debugtokenrequest-check and he didn't tell me something unusual no more.

  So, what could cause this problem?

  Are you using the PIN exactly as there are shown on the PlayBook (do not convert this number to hex)?  The number would already be in hexadecimal.

  The date on the PlayBook should be synchronized with your PC.  If the date of the PlayBook is prior to the date of creation of a token of debugging or 30 days after the time of creation of a token of debugging, it will be invalid.

  Can you confirm these two?

• Debug token frustration

  Could there be any more hoops to jump through to test a program on the material that I own, here in front of me?

  What is this token of debugging, how do you get one, and how to set up and used, please?

  Looks like I tried to access a military satellite.  Everything I'm doing is printed 'Hello There' on the screen of a toy that is not even on a telephone system.

  I found this a good explanation (including a video of very detailed step by step by Julian Dolce):

  http://deleteaso.com/PlayBook-debug-tokens-and-signing/

  Anna

• Debugging token is invalid

  This mistake will kill me lol.

  I already signed the file .bar and everything. With the help of "blackberry - deploy - installDebugToken BarFile.bar - XXX.XXX.X.XX - password password device»

  He tells me that...

  Info: Send request: install Debug Token
  Info: Action: install Debugging token
  Info: File size: 275850
  result::success

  While it appears in the game as book

  Debug TokenInstalled

  ValidDebug token is invalid

  Author

  Expiration

  The date and time correspond with my computer exactly. The and are correct. Idk what it could be . Tried to roll several times.

  It seems that your BarFile.bar is not even a token of debugging file.

  You should consult the documentation on that. You must have created a token debugging using "blackberry debugtokenrequest" and specified the PIN code of your tablet. Located in the settings under on-> hardware.

  This will create a file .bar with debugging token inside. It has nothing to do with your application, which is what I guess it is in the file BarFile.bar. You then install the .bar token of debugging with the command that you were trying initially.

  Please read the docs, unless you know all this, and the issue is something else. I just checked with the "-check" command in a file of .bar app and it gave the same results you have seen. On a debug token .bar file he would act differently.

• Unable to create a debugging for my playbook device token

  Hi all

  I have a problem to create a debugging token to install on my playbook.

  * I installed the SDK for a long time (before the playbook was here), when I installed first of all, there was no debugging token / COMINCO files

  * Then I received my COMINCO file by mail, but has not used as I was more accustomed to using the Simulator.

  * I have since released an Android application.

  I have some barsigners files in the folder "C:\Users\MY_NAME\AppData\Local\Research In Motion". I think that they were created when I published the Android app.

  So now when I try to create a token of debugging with this command:

  BlackBerry-debugtokenrequest - storepass XXX - XXX c:\temp\debugtoken.bar devicepin

  And I have this error:

  Error: The signature on the request of code signing did not check. The probable cause of this problem is entered a wrong password CSK.

  My store is correct (I have another error if I intentionally use a wrong password).

  Can this be my PBDT.csk file that is not registered?

  How can I change this?

  Thanks for any help,

  I need it because I now have a bug that does not intervene in the ripple or on the simulator of the tablet.

  Emmanuel / Alocaly

  OK, the different password for the developer certificate (p12) and RIM Code signing key would cause problems here.  Rename your author.p12 to something else and create a new p12 with the same password as your Code RIM signing keys.  Do not delete the barsigner files or you will not be able to sign the upgrades of your applications.  This command will allow you to create a new file p12.

  blackberry-keytool -genkeypair  -storepass  -dname "cn="
  

• Cannot download app even if PlayBook has a debugging token

  So my old debugging token has expired and I decided to start a new

  I followed the following link

  http://docs.BlackBerry.com/en/developers/deliverables/23959/Create_a_debug_token_using_FB4.5_1585073...

  but every time when I try to run my application on a playbook I get this:

  Deployment failed: send request to install it...
  Info: Action: install
  Info: File size: 2253635
  Info: installation...
  Info: Treatment 2253635 bytes
  actual_dname:
  actual_id:
  actual_version:
  result::failure 550 ApplicationModeMismatchError

  Nothing in Google on this subject. Could someone give some advice how to fix this or what to look for?

  Thank you

  p. s.

  Yes my authorid is in blackberry - tablet.xml and it is the same as that in my debugging token.

  Found a solution.

  Weird enough but clear Application Data on the next launch should be turned off whenever I sent an application to run on my Playbook (in... a series of section Configuration)

• How to deploy webwork debugging token on playbook?

  How to create and deploy webwork debugging token on playbook?

  What is the command and the path?

  BB10, is blackberry-debugtokenrequest - storepass - devicepin... *. bar..

  BlackBerry-deploy - installDebugToken...

  The following URL should have what you are looking for: https://developer.blackberry.com/html5/documentation/loading_your_app_to_playbook_1866988_11.html

  Make sure you use the tools to create and deploy the token in the SDK of WebWorks PlayBook not BlackBerry 10.

• Debug the invalid token

  I can create a debugging token and see it in flash builder, and with the command line tool. There is no errors during the creation process, and it contains the correct PIN code for my playbook.

  When I download (the .bar file) to the device, I get 'no' next to validate, and the author and expiration fields are left white. I followed the instructions that came with the .csj file, both versions of flash builder and the command line. I also tried following the tutorial video. In any case, I have the same problem.

  Obviously, I'm doing something wrong. Can anyone suggest what I might be missing.

  Thank you

  Andrew

  Resolved:

  The problem is, I didn't properly set the date on my PB. I created the token may 5, but the PB date is something April. Changed the date and it works very well.

• Question of BB10 Dev Alpha: debugging token is invalid

  I'm trying to get a token of debugging on my dev alpha device and it just cannot work. I can create, validate, and install the token, but it generates an error: debugging token is not valid. Or not applicable for this device.

  10.0.4.197 OS version

  Build ID: 196525

  PIN: 29D939F4

  Start: 28 June 21:32:34 UTC 2012

  I use BlackBerry 10 WebWorks SDK 1.0.0.15

  I just restarted the device. It is currently 21:26 according to my computer clock and the BB10 clock is synchronized with the clock of my computer... it of doesn't look right... the listed start time is 5 minutes in the future.

  Here's what I did.

  blackberry-debugtokenrequest -storepass storepass -devicepin 29D939F4 debugtokens\BB10_Dev_Alpha_debugtoken_29D939F4.bar
  

  Info: Debug token created.

  blackberry-debugtokenrequest -verify debugtokens\BB10_Dev_Alpha_debugtoken_29D939F4.bar
  

  Issue date: 28 June 2012 02:02:59 CEST
  Expiration date: 28 July 2012 02:02:59 CEST
  Features:
  702102004

  Info: Debug checked token.

  I checked the device PIN above (702102004) is correct. This is the decimal version of my device PIN (29D939F4)

  I tore the debugging, and here's the manifest token:

  Archive-manifest-Version: 1.2
  Archive-created-by: BlackBerry BAR package v1.4

  The package author: XXXX
  Package name: debug.token
  Package version: 0.0.0.8
  Package-Type: debug-token
  Package-author-certificate-Hash: XXXX
  Package-author-Id: XXXX
  Package-Id: XXXX
  Package-Version-Id: XXXX
  Package - Issue Date: 2012-06 - 29 T 00: 02:59Z

  Debug-token-system-Actions: run, multi_window, multi_instance, run_air_native, run_native
  Debug-token-expiration Date: 2012-07 - 29 T 00: 02:59Z
  Debug-token-device-Id: 702102004

  I was thrown for a moment of the date (Date of show-package -: 2012-06 - 29 T 00: 02:59Z) until I realized it was just

  my current time converted to offset - 0. I am currently in Toronto, where it is now UTC - 4.

  blackberry-deploy -installDebugToken "C:\Program Files (x86)\Research In Motion\BlackBerry 10 WebWorks SDK 1.0.0.15\debugtoken.bar" -device 169.254.99.117 -password password
  

  Info: Send request: install Debug Token
  News: Expired session reset
  Info: Send request: install Debug Token
  Info: Action: install Debugging token
  Info: File size: 2273
  result::success

  Yet, the device don't like this token. Here is the result.

  

  Any ideas to know what could be the problem here?

  Thank you

  Stem

  Rod,

  I had the same problem with my alpha chips and debug dev. Setting date/time is the source of the problem.

  Here is the fix:

  • The mode of development
  • Set your date/time to June or the date in the past.
  • Check your token security and debugging
  • Debugging token becomes valid

    My date is June 25

  Let me know if this solution worked for you! Worked for me.

  

• Debugging token (s)

  I followed the instructions on creating a debugging token and to load in my PlayBook, however when I go to settings and look, it shows the token as not valid and expiry and the author are empty. I also get no signed bar error when deploying my application, but I don't know that this is because the invalid token. I tried to come back and create a new token in FlashBuilder Burrito but when I try to create it, it gives the error "the certificate file does not exist. I get this error if I create a new certificate (in the default or custom location) or if I import a certificate. I know that my certificate is valid because I use it to sign a release build very well. Any help would be appreciated as to why he throws this error.

  Nevermind, I got it to work. I had to first create the file and save it, then open it up to use it. Probably should have tried first.

• Error: Not yet registered to request debugging tokens

  "I wrote my small and simple application in HTML5 and bundled with the ripple (with 1 WebWorks) emulator (without signature), but after trying to install the .bar through DDPB file it gave me the error ' 881 found no debugging token. Now, previously, I had already a debugging token on my Z10, but as the nube I'm kidnapped by accident. Now, while trying to recreate the debugging token, I encountered error in cmd, ' error: not yet registered to request debugging tokens. I have an author.p12 file, a barsigner.db file and a bbidtoken.csk file that I had tried to help out, I'm getting lost in all the documentation which has provided Blackberry and probably have 1 million junk files, could someone please help me get back on track.

  Sorry for the nube-nish, I'm only 13...

  WebWorks 1.0 will not support BBID approach to signature, if you go this route you will need to request a new set of files of the LSB of the code signing the form here:
  https://www.BlackBerry.com/SignedKeys/Codesigning.html

  When you ask for the keys, don't forget to check this box:
  For BlackBerry PlayBook apps or BlackBerry 10 apps development SDK lower or average of a 10.1 or BlackBerry 10 SDK WebWorks less than 2.0.

  In an hour or two, you will receive two files CSJ. Before you begin installation, ensure that the directory that houses your key is empty (records can stay.) I recommend to copy all existing files in a folder "backup" just in case, but don't want any old CSK, DB, etc. of generated files cluttering it. If you do not know what directory, check the "files backup" section here that lists the directories.
  https://developer.BlackBerry.com/HTML5/documentation/v1_0/signing_setup.html

  Once emptied, you can use the steps in this URL (top of page) to save your CFS files. Essentially, by running the command of blackberry-signatory to record your keys.

  Once this is done, you should be able to generate debugging tokens and others. The important part is to no BBID and mixture LSB file, and does not support this WebWorks BBID 1.0.

• I couldn't get a debugging token

  Hello!

  I'm Charlotte of Spain (and I speak very well English)

  I'm trying to get a debugging token for blackberry Playbook, but I don't know what the problem is when I use blackberry-debugtokenrequest, because he said that I have to be registered and I registered on the blackberry, I think its possible that I need to be registered as a vendor, but I'm not sure.

  I have another question: I'm developing an application in marmalade, but I don't know how to make it work in my playbook, the problem said that I need a "BlackBerry ID author:

  ERROR: Info: Package created: C:\Users\Juanma\Documents\Quick\Projects\MyFirstApp\deployments\default\playbook\debug\MyFirstApp.bar
  Error: bar4048788377155908783. MF, validates the value package-author-ID 'Juanmabs22'.

  I guess I need the debugging token to try it, but I'm not sure.

  Thank you!

  

  The SJC files have been installed on another computer?  They can only be installed once.  If so, use the backup and restore procedure for copying on your other computer.

  Backup and restore BlackBerry Code signing keys

• Signatory of bar - Debug tokens, create fails, import does nothing

  In Eclipse, Preferences, BlackBerry, BlackBerry SDK tools, Bar signatory both create and import fail (in a slightly different way). It comes with the new tools of 1.3 released this week.

  Create has always been broken (for me both v1.2 and 1.3 tools), where it still shows the certificate of loading error: java.io.IOException: key topic, java.security.InvalidKeyException: invalid key CE.

  Advice on another forum entry, work-arround is to manually create a debugging token using the blackberry-debugtokenrequest tool.  This process with an import, worked under Tools v1.2 (at least once).  Now with a new device I created a new token of debugging with the new device ID and he gave a new file name. When I try to import into. I get the 'in progress' for about 5 seconds operation"and then the dialog box disappears and information has NOT been added to the list of tokens of Debug (so I can't download the token).

  During the process, I have only the new attached device (a Dev B device with active debugging).  I use Windows 7 x 64 SP1 with Eclipse SP2 Indigo and BlackBerry taken into 1.3.0.201209131728, Java 7 update 7.  I have all the latest update in Eclipse. Another note, during an attempt to create, it automatically detect the device and shows the right PIN device if you can see the device.

  Any ideas?

  Good idea. I couldn't find any 32-bit command-line tools, but I just copied the files in the 64-bit directory in a folder in the "Program files (x 86)" assumming they run in both modes. I managed, but I don't know if the "32-bit" operation makes no difference. I came across the same problem as before, but I understand an alternative that worked as follows. It is a different process as described in the documentation.

  Start with a token created debug created via the command line utility (blackberry-debugtokenrequest) for your specific device (in my case, a Dev Alpha B). Have the device connected via the USB port and within the parameters of the device, secuity, Mode of development.

  In the Eclipse-> BlackBerry preferences-> BlackBerry tools-> target.  The (default) usb item should appear in the list. Select it and then press the button of Details Token debug, and then select Import.  Point to the file debug token you already created.  Once completed, he must invite to download the token to the device, I did. Success at last!

• Can't download debugging tokens

  I finished my registration key and has managed to create a token of debugging but now cannot download the token for the Playbook. The application crashes for a while when I try to download the token and then throw the cryptic "error in loading the debugging tokens". It's very frustrating because I'm not sure what to try next. A Unix solution will be useful?

  I'm on a Mac OS 10.6.7 using Flash Builder Burrito, Blackberry sdk 1.0.1 and Air 2.6 sdk. I am aware you need to force the compiler to use air 2.5.

  Download of a token of debugging via flash builder 4 has not worked for me too, until I had who abandoned and deployed via the console. and it worked. have you tried already?

• Suddenly unable to create debugging tokens.

  Here is what happened.  The end of August, I was able to create Momentics debugging tokens and download them on my Z10 to test my application.  I went on vacation, I saw that my token had expired and tried to create a new token.  When I launched the Momentics app it would create the token, I would put in the p12 password, then he repeatedly asks the password of KSB.  After a number of times I see this error

  An internal error occurred during: "Creating and debugging token download.".
  java.lang.NullPointerException

  And no token would be created.  I tried to start the creation of the command line debugging tokens, but it failed with this error

  Error: Illegal device ID XXXXXX

  Oh yes, before I realized that my token id had a year so I downloaded a new and saved in the directory ResearchInMotion down AppData.  Another thing I tried after that his return was linking my old keys to my account.   I couldn't remember if I had done a few years before, when the last one, I worked on the application, but the process never seems to succeed this time.  And I use the words-> hardware-> PIN PIN

  I got things to work.  When I was downloading the bbtokenid I was going on the site and generating here and downloading it and then copy the file to the AddData/local/research... folder.  Instead, I entered Momentics, window-online Preferences => BlackBerry-online signature and downloaded the new token there and created the debugging file.  I suppose that in view of the old author.p12 and other files, but the new bbtokenid on the site does not work.