Creating a debug token issues

Similar Questions

• Cannot create the debugging token

  Hello world

  Being new to BlackBerry, but not to programming I wanted to create some apps, but that's where the problem began:

  I'm not able to create a debugging token.

  Momentics IDE using:

  Matching and signature succeeded.
  The message I get is: "error creating debug token".

  Thanks to the usr\bin\ tools

  I was able to create the file author.p12 to sign with blackberry-keytool
  But using blackberry-debugtokenrequest I was not able to create the debug token file. The syntax used is listed below (1). It tells me that devicepin is not found.

  Using (2) I get "error: the password of csk specified is not valid.

  Changes of "author.p12 path" - keystore adding nothing

  Adding the 'path of the bbidtoken.csk file' results - cskpass in the above error

  By using the token in the file .csk instead of the path the console does not complete the command and locks into place. (Ctrl + C still works)

  System 8.1 Win x 64, Java is x 86, used x 86 powershell for orders

  If anyone can help, that would be really appreciated.

  (1)
  BlackBerry-debugtokenrequest - storepass (-devicepin ) + []

  I use the old AIR SDK to create debugging tokens, but I also creates the chips on the command line, the call should be similar. That's what I do

  blackberry-debugtokenrequest -cskpass %1 -keystore %2 -storepass %3 -deviceId %4 newDebugToken.bar
  

  where

  %1 = password of the cskfile

  %2 = your keystore .p12

  %3 = password of the keystore

  %4 = the hardware of your device id as hex (don't forget 0 x)

  Also note that there is no «»

• command line to create the debugging token has problem with the bbidtoken

  Hello

  I tried to use the BB ID token to create the debugging token.  Following the instructions of the command line, I got an error.

  BlackBerry-debugtokenrequest - bbidtoken bbidtoken.csk - storepass mypassword deviceid - 12345678 dt.bar

  Error: Only RDK or COMINCO Signatures are allowed when using BBIDToken

  The token id BB must be correct, because I can use it to sign an application.  I can also generate the debugging token from Momentics.  I believe momentics also call blackberry-debugtokenrequest internally, but do not know what are his secret settings.

  Thanks in advance for any help.

  Tyler

  Try without the parameter of bbidtoken.csk - bbidtoken.

  Also, make sure you use blackberry-debugtokenrequest of the 10.2 Gold SDK.  Previous versions do not BlackBerry ID support chips.

• Cannot create the debugging token (.bar)

  Hello

  A few months ago I got xxx.csj - RDK-client and client-COMINCO - xxx.csj and registered with blackberry-signer. I used them to sign my applications published in the world of Blackberry. Some time later, I registered author.p12, barsigner.csk, and barsigner.db in a place course and then reinstalled my Windows OS.

  Today, I tried to create the debugging token. If I run:

  C:\bbndk-2.1.0\host\win32\x86\usr\bin\blackberry-signer-s'inscrire - csjpin - storepass xxxxxxxx xxxxxxx customer-RDK - xxxxxx.csj customer-COMINCO - xxxxx.csj

  I get an error:

  Cannot save client xxxxxxx because there is no more the record attempts. If you are already registered with this server, you must restore your backup signing keys. If you do not have a backup of the key, then you can order a new set of keys at www.blackberry.com/go/codesigning

  OK, I have my author.p12, the barsigner.csk and the barsigner.db, so I tried:

  C:\bbndk-2.1.0\host\win32\x86\usr\bin\blackberry-debugtokenrequest cskpass - xxxxxx - keystore author.p12 - storepass xxxxxxxx - deviceId xxxxxxx debugtoken.bar

  I get an error:

  Error: Not yet registered to request debugging tokens

  What's wrong? How can I generate a debugtoken (.bar file)?

  Oops! My mistake, I forgot to copy author.p12, barsigner.csk and barsigner.db to the default location:

  C:\Users\\AppData\Local\Research in motion

• Can't remember how to create a debug token

  In previous versions of the SDK, I didn't hurt to make it past the stage of creating a debugging token, but for 10.0.9 I am stuck.

  A dialog box appears allowing me to select my developer certificate, what I do, but it's also requires me to fill:

  Path of the CSJ RDK

  Path of the COMINCO CSJ

  CSJ pine

  Password: CSK

  Previously I remember only having to enter the password of the CSK.

  Anyone know what is happening?

  I had to go to:

  Window-> Preferences

  BlackBerry

  Signature

  Clicked: The deployment of the BlackBerry installation wizard

  etc.

• Cannot create the debugging token / deploy Release - version signature of server problems?

  Since yesterday, Momentics IDE fails to create debugging tokens / binary deploy to exit with the error ' cannot sign bar: server is not responding.

  Is the signing server down? What is going on?

  The network connectivity problem is resolved.  If you had problems signing or debugging tokens created, please try again now.

• Ripple Emulator - construction and launch - no launch - Debug token issue

  It's a piece of help and advice for you all so fall you on this

  After you install the emulator of ripple correctly using the download here:

  https://developer.BlackBerry.com/HTML5/download/ripple

  And don't forget to follow this document:

  https://developer.BlackBerry.com/HTML5/documentation/ww_getting_started/Use_the_Ripple_emulator_Chro...

  I got a job of waving emulator.

  Also I could pack my application, but try to launch it directly on my device BB10 Dev Alpha never happened.

  No error displayed I had no idea.

  Using the graphic help trying to install the created device / .barhe told me that the author does not match the token author correction.

  Which is strange, I had copied this author name 1-on-1 for the config.xml file.

  After doing a manual generation using the. / bbwp v1.0.0.7 BlackBerry WebWorks SDK resources, I have seen that he has failed to get the debugging token.

  As I had not seen anything in the documentation I took a wild guess and copied on my debugtoken in the same directory the. / tool bbwp resided.

  This corrected the manual version and also the option Package and laugh in the emulator to ripple.

  If the solution is to copy the peripheral debugtoken BB10 Dev Alpha V1.0.0.7 of SDK BlackBerry WebWorks directory.

  If this is something that must also be saved in the incident handler, please let me know.

  Hope this helps some of you running into the same wall.

  To solve the problem that the package one implemented does not when you deploy directly to your BB10 Dev Alpha device, copy the file debugtoken.bar in the directory of BlackBerry WebWorks SDK V1.0.0.7 where als othe. / bbwp resides.

• 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.

• 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="
  

• 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!

• 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.

• Where the IDE does not store the debugging token?

  I try to use a different method to compile applications but I'd like to avoid re-creating the debugging token

  When you go to the "signature" tab (preferences-> OS BlackBerry Tabel-> signature), the token path debugging is listed for her.

• Download the Debug token error

  I try to install the token of debugging on my device. I've added as a Test device with the password WiFi IP address and device. I also created a debugging token. When I try to download to the device (when the appliance is in Mode Token Upload), it takes a long time and I get an error indicating that the download failed - connection refused.

  I checked the symbolic debug information and everything seems fine. I also tried to download the token via command line, but I still get connection failed.

  Any ideas?

  Nevermind, after three days of troubleshooting, I was able to install it. It was just a problem of network.

• Lost the ability to create tokens of debugging: error: Code signing request has failed because the value debug token of Type Package is not allowed.

  I have been a token of debugging and apps on my device Z10 hundreds of times from the command line and Momentics but this time I am confused.

  I am trying to create a token of debugging (in command line and Momentics) and deploy it in my Z10 camera, but it does not work.   In both cases, I get the following error.

  "Error: Code signing request has failed because the value debug token of Type Package is not allowed."

  2 things have happened recently that make this potentially different situation.

  a.) now my device is currently running OS 10.2

  (b) there was something new regarding signing apps with your blackberry ID?

  I was a little out of the loop for 1-2 months so please forgive me if this problem is very obvious... I am looking for a clue to what I'm doing wrong.

  This has been fixed on both of your accounts.  It was a problem of account setup.  We're looking at what caused it to prevent it from happening in the future.

• Error creating debug token

  Hello

  I recently downloaded BlackBerry 10.1 SDK with QNX Momentics. To simply run a program in my camera (connected device Q10), I registered with success code. But when I try to get the debugging token, it gives the error as pictured. I have both try in Mac and windows, it gets the same problem. And the error is not informative, it gives the error error: null: null

  

  

  

  I solved today. With the other computer, I downloaded QNX Momentics IDE (10.1) with native SDK. Creation of debugging in QNX Momentics token give back the same error (error: null error: null). However, I tried manually with command prompt and debugging token created with success this time. I then imported it with the IDE.