The Debug Token can be uploaded to the BlackBerry PlayBook to allow unsigned applications to be run on the device. Once uploaded it can be viewed from the following menu:
Options > Security > Development Mode
Under the Debug Token header you should see a list of information regarding the debug token: installation state, validity, expiration date and author.
After creating a Debug Token and uploading it to the BlackBerry PlayBook it may show as Installed but with the Valid status set to "No". If this is the case then the remaining field, Expiration and Author, will display blank values.
The Debug Token has 2 date values set when it is created:
These can be viewed by opening the BAR file using an archive program then opening the MANIFEST.MF file, located in the META-INF directory, in a text editor. If the date set on the BlackBerry PlayBook is outside the range of these 2 dates then the Debug Token will be seen as invalid.
Ensure that the date and time on your BlackBerry PlayBook matches the time on your Computer. Even being a few minutes off could cause the Debug Token to be seen as invalid until the Package-Issue-Date has passed.
If the computer date is incorrect then you should likely delete any current Debug Tokens and generate new tokens once the date is corrected.
Debug tokens are tied to preconfigured PINs of BlackBerry PlayBooks. If you install a debug token onto a BlackBerry PlayBook that does not include the PIN of the BlackBerry PlayBook, the debug token will appear as not valid.
Create a debug token that includes the PIN of the target BlackBerry PlayBook and install this on the device. Debug tokens can contain one to many PINs.