Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Testing and Deployment

Troubleshooting: Common failure reasons while deploying applications to the BlackBerry PlayBook simulator

by Retired on ‎03-16-2011 02:16 PM (3,841 Views)

As described in the BlackBerry Tablet OS Application development guides (Getting Started – Adobe AIR; Getting Started - BlackBerry WebWorks), deploying an *.bar BlackBerry® PlayBook™ Tablet application to the BlackBerry® Tablet Simulator requires the following 2 steps:



  1. Enable development mode on the target Simulator
  2. Use the blackberry-deploy service, found within the BlackBerry® Tablet OS SDK, to deploy your *.bar application to the simulator:



blackberry-deploy -installApp -password <simulator password> -device <simulator IP address> -package <BAR file path>



If your deployment is successful then output, similar to the following, will be displayed in the command window:



Sending Install request...
Info: Action: Install
Info: File size: 41978
Info: Installing ...



However, if the blackberry-deploy utility was unsuccessful while deploying the *.bar file to the simulator, then a result code of “failure” will be displayed along with a corresponding error message:



Error: Connection to refused.


The following are common failure conditions that may occur while attempting to deploy an application to the BlackBerry PlayBook simulator:


Failure Message Reason / Solution
500 navigator interlock failed

Reason: A version of the application is already in use on the BlackBerry Tablet OS


Solution: Wait for the BlackBerry Tablet OS to release lock on the application and then use blackberry-deploy –uninstallApp to delete the application. May require an OS restart.

Connection to <IP address> Refused.

Reason: #1 An active VPN connection may be blocking deployment.


Solution #1: Disable VPN before deploying the application.


Reason #2: Incorrect IP address used


Solution #2: Verify that you are using the correct IP address of the active connection.  If you see two IP address listed in the Development Mode window, try the other one.

Cannot connect: Connection to https://<IP address> refused. You may have to reboot the target.

Reason #1:  The BlackBerry Tablet OS is not responding.


Solution #1: Reset the target device.


Reason #2:  The device password is not longer accepted by the blackberry-deploy service.


Solution #2: Clear the device password and set it again.

Username or password is invalid or not specified or time on the device is out of sync

Reason #1: If the VMPlayer was suspended, rather than the BlackBerry Tablet OS VM being shut down, the timestamp of the BlackBerry Tablet OS may be out of sync with that of the host PC.


Solution #1: Update the BlackBerry Tablet OS system time to match that of your development machine


Reason #2: The simulator device password, used during development mode, is incorrect or expired.


Solution #2: Verify and/or update the device password to ensure it is correct and not expired.


Reason #3: The version of the BlackBerry Tablet OS SDK used to deploy the bar application and version of the target BlackBerry PlayBook simulator are out of sync.


Solution #3: Ensure the version of the BlackBerry Tablet OS SDK used is the same as the version of the BlackBerry Tablet OS.

Device is not in the development mode.  Switch to Development from Security settings on the device

Reason #1: The Simulator has not been enabled to use development mode.


Solution #1: Open the gear icon from the task bar and select the Security option tab.  Look for a “development mode” selection and switch the switch from “Off” to ”On”.

Invalid Auth Credentials

Reason: May occur after upgrading your BlackBerryTablet OS simulator but while still running an older version of the BlackBerry Tablet OS SDK.


Solution: Upgrade BlackBerry Tablet OS SDK to same version of Simulator (recommend upgrading both to their latest available versions)

500 development apps pool exhausted

Reason: You can only have 10 installed at a time in development mode.


Solution: Remove unused applications from the virtual machine before deploying your application

Users Online
Currently online: 32 members 3,785 guests
Please welcome our newest community members: