Known issues for BlackBerry Plug-in for Android Development Tools

‹ Back to Release notes for the BlackBerry Plug-in for Android Development Tools for Eclipse.

Issue

Workaround

If one instance of the BlackBerry Plug-in for Android Development Tools for Eclipse is installed with Android Development Tools version 23.0.x, and another instance of the plug-in is installed with the Android Development Tools version 22.6.x, the instance with version 22.6.x is not operational.

Have only one instance of Eclipse with the BlackBerry Plug-in for Android Development Tools for Eclipse installed on your computer.

In Ubuntu 14.04 OS, the BlackBerry Signing Authority Tool might not be able to start the browser to obtain a BlackBerry ID signing token.

If you cannot click the URL, select the text and use copy/paste to copy the link into a browser window to proceed with the signing registration.

If an unsigned .bar file of a repackaged Android app is installed on the BlackBerry 10 Device Simulator, trying to deploy the app to the BlackBerry 10 Device Simulator through “Run” or “Debug”, causes an ApplicationModeMismatchError error.

None available.

When debugging in Eclipse with the BlackBerry 10 Device Simulator or a BlackBerry 10 device, the Debug perspective in Eclipse does not open, breakpoints are not hit, and the error "Launch error: Failed to connect to remote VM" is reported in the Eclipse log files.

One possible workaround is to change the default value of the Android debugger from port 8600 to another port number.

To change the port number in Eclipse:

  1. Navigate to Window > Preferences > Android > DDMS.
  2. Enter a new value for the port number in Base local debugger port.
  3. Restart Eclipse.

The BlackBerry ADB Proxy Manager cannot establish a connection to a Wi-Fi IP of a BlackBerry 10 Z3 (JAT) device running OS version 10.2.1.3181.

Connect the device with USB.



Got questions about leaving a comment? Get answers from our Disqus FAQ.

comments powered by Disqus