Testing your repackaged app on a BlackBerry device
Although the apk2bar and apk2barVerifier tools can help you to determine how well your app is likely to work on a BlackBerry PlayBook tablet or a BlackBerry 10 device, they are no substitute for loading and testing your app on a device. At this point in the process, your apps are repackaged as BAR files, but they are not signed. Signing is a security measure required before any BAR files can be distributed to BlackBerry users using the BlackBerry World storefront.
You can test your unsigned apps on your BlackBerry device using a debug token. A debug token must be created by an individual or organization that has permission to sign applications for the BlackBerry Tablet OS or the BlackBerry 10 OS. You requested this permission when you requested a code signing key.
When you create a debug token, you specify the PIN for each device that the token is valid for. You can specify a maximum of 100 device PINs across all of your debug tokens that are currently active. If you need to specify more than 100 PINs, you must wait for some of your debug tokens to expire before you must create more.
A debug token is valid for 30 days. When a token expires, the BlackBerry Tablet OS and the BlackBerry 10 OS no longer allows unsigned applications that rely on that token to run.
To test an unsigned app on a BlackBerry device, first you must create the debug token and upload it to your BlackBerry device. You can then load your app on your tablet and test the functionality.