Application Deployment may hang or fail after OTA Update to 10.1.

by Retired on ‎06-14-2013 02:02 PM - edited on ‎12-23-2013 10:05 AM by Retired (3,731 Views)


After an OTA upgrade to 10.1, developers may find that they are no longer able to deploy applications onto the device using the SDK.


The console may look like this:

Deployment Failed: Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: File size: 205384
Info: Installing com.example.AAAA.testDev_xample_AAAA306be591...
Info: Processing 205384 bytes

At this point the deployment may hang and fail with a timeout.



This issue is resolved in BlackBerry 10.2.



In order to deploy applications onto a device affected by this issue, you may use the blackberry-deploy -uninstallApp command with a package name that does not exist. Running this command every X seconds in the background while deploying an application should allow for successful deployment.


To automate this, you can use the attached batch/bash script. This script runs an uninstall command on a package name that does not exist every 50 seconds, to keep the installer alive. This should allow the application to deploy. Once the application is deployed, you may close (CTRL+C) the script.




1. Extract archive that applies to your OS

2. Open the script using Notepad

3. Edit the SDKBINPATH variable to point to the bin folder of the SDK, depending on your environment:


BlackBerry® 10 WebWorks™ SDK:


Example: C:\Program Files (x86)\Research In Motion\BlackBerry 10 WebWorks SDK\dependencies\tools\bin


BlackBerry® 10 Native SDK:


Example: C:\bbndk\host_10_1_0_212\win32\x86\usr\bin


BlackBerry® 10 SDK for Adobe® AIR®:


Example: C:\Program Files (x86)\Research In Motion\blackberry-tablet-sdk-3.1.3\bin


Note: please ensure SDKBINPATH does not have a trailing slash.


4. Edit IP if device IP is different from

5. Run batch script > enter password

6. Leave running in the background while you deploy your application

7. Hit CTRL+C once the application is deployed


If you are having issues locating blackberry-deploy in the above paths, you can perform a search and locate them manually.