Test your unsigned application on a device
If you want to test an unsigned application on a device, you must create and install a debug token on the device and configure the bar-descriptor.xml file.
You can use the commands in the following table to create and upload the debug token through the command line tools.
| Argument | Value |
|---|---|
| -cskpass <CSKpassword> | This argument specifies the password that you defined when you configured your computer to sign applications. |
| -keystore <certificateName.p12> | This argument specifies the location and file name of the developer certificate that you created when you configured your computer to sign applications. |
| -storepass <keystorePassword> | This argument specifies the password that you defined when you created a developer certificate. |
| -deviceId <yourDevicePIN> | This argument specifies the PIN of the device that you want to install the debug token on. For each PIN, use the prefix 0x. For example, if your PIN is 100ABCD, then enter: -deviceId 0x100ABCDTo specify multiple devices, specify this argument multiple times or create a text file that contains a list of device PINs and use the -deviceidlist argument. |
| <debugTokenFileName>.bar | This argument specifies the file name of the debug token you want to create. The debug token file name must end with a .bar extension. If you specify the name of an existing file, the blackberry-debugtokenrequest tool deletes the existing file before it creates the debug token. |
| -installDebugToken <yourDebugToken.bar> |
This argument specifies the location of the debug token .bar file that you created. |
| -device <yourDeviceIP> |
This argument specifies the IP address of the device. |
| -password <yourDevPassword> | This argument specifies your device password. |