Sorry about the red box, but we really need you to update your browser. Read this excellent article if you're wondering why we are no longer supporting this browser version. Go to Browse Happy for browser suggestions and how to update.

BlackBerry Java Plug-in for Eclipse v2.0

Known issues

This section lists the known issues for the BlackBerry Java Plug-in for Eclipse v2.0 for Windows and for Mac OS X. The issues described below occur on both platforms, unless noted otherwise.

Installation

Issue

Workaround

Windows only. If you install the BlackBerry Java Plug-in for Eclipse in a folder with name containing two or more consecutive spaces, an error occurs in which the simulator cannot run. (5079392)

Install the BlackBerry Java Plug-in for Eclipse into a folder with no spaces in the name.

Debugging

Issue

Workaround

Mac OS only. When you debug dependent projects using the default JVM for Mac, an error displays. (5079370)

Change the JVM of the dependent projects to SDK 7.0.

Windows only. The simulator crashes when you relaunch the disconnected RIM JVM. (5079458)

Re-launch through the launch configuration.

Mac OS only. Deleting locale resources throws an illegalArgumentException while debugging on a BlackBerry device. (5079361)

Remove and the redeploy the application.

Windows only. When you debug a BlackBerry 7.0 application project that contains breakpoints on a BlackBerry smartphone, if you terminate the debug session and then debug the app again, the first break point is skipped. (5079359)

Redeploy the application.

Windows only. When you debug a BlackBerry application project on the BlackBerry Smartphone Simulator you may encounter a connection timeout. (5079357)

Increase the amount of system RAM to a minimum of 4 GB.

Windows only. When you debug a BlackBerry device application after the application encounters a break point, when you open the Variables view you might encounter the message: not available - unsupported by VM for some variables. (5079335)

Expand the variable to observe other inner fields or debug your application by using the BlackBerry Smartphone Simulator.

When you debug your BlackBerry device application by using step filtering, Filter by Package does not work. (5079283)

After you select Filter by Package, click Window > Preferences > Java > Debug > Step Filtering; check the Use Step Filters check box.

Mac OS only. When you debug a BlackBerry device application on a BlackBerry device, after your application stops at a break point, when you click resume, the debugger may stop responding. (5079435).

Restart the BlackBerry device and begin a new debug session.

Mac OS only. When you debug a BlackBerry device application using the BlackBerry Profiler View, if you click the rows inside the view multiple times, Eclipse may freeze or close. (5079281)

Close the debugging session or restart Eclipse.

When you hot-swap a BlackBerry device application that uses resource keys, if you change a resource key, the application is not updated when you resume hot-swapping. (5079277)

Close the application before hot-swapping.

When you debug your BlackBerry application on a simulator by hot-swapping, if you remove a field from a persistent instance, when you relaunch your application, hot-swap does not stop at the break point. (5079429)

Delete and redeploy the application. You may also need to restart the simulator.

When you create a BlackBerry device launch configuration and select the option to attach to a specific device, the BlackBerry Java Plug-in for Eclipse does not prevent you from starting to debug without specifying the device. In addition, the list of available devices may not always reflect the devices that are currently attached even after selecting the option to refresh the list. (5079259)

Do not create a device launch configuration that attaches to a specific device without specifying the device.

BlackBerry Smartphone Simulator (Windows only)

Issue

Workaround

When you run a BlackBerry 7 application project that requires HTTP, the BlackBerry MDS Simulator fails to start. (5079373)

Set the JAVA_HOME environment variable to the directory where you installed the Java SDK 1.6, and add %JAVA_HOME%\bin; to the beginning of the PATH environment variable string. If you have the Java SE 7 development kit (JDK) installed, make sure it is not the default or uninstall it.

On a computer running Windows 7 (64-bit), when you use the BlackBerry Smartphone Simulator for the BlackBerry Java SDK 7.1, after you add data to non-volatile storage (for example passwords) or the file system (for example contacts), when you clean the simulator the files are not removed. (5079442)

Remove the files and data manually.

When you run or debug an application that automatically starts MDS-CS using the BlackBerry Java SDK 7.0, if you terminate the BlackBerry Smartphone Simulator, MDS-CS does not stop. (5079455)

Terminate the process manually.

When you run Windows 7 64-bit, if you test your BlackBerry device application on a BlackBerry Smartphone Simulator that you installed outside the Eclipse environment in an access-controlled directory, contact and password information may not be deleted when you run Clean Simulator. (5079442)

Open using Run as administrator when you install a BlackBerry Smartphone Simulator and when you use the BlackBerry Java Plug-in for Eclipse.

After you install an external BlackBerry Smartphone Simulator, when you run or debug your BlackBerry device application, the BlackBerry devices that are supported by that simulator appear in the list of available devices even if the devices are not supported by the selected BlackBerry JRE. (5079307, 5079309)

Select a device that is compatible with the BlackBerry JRE and the BlackBerry APIs that you use in your application.

When you run a BlackBerry device application in the BlackBerry Smartphone Simulator, if you launch the application a second time using a different BlackBerry JRE, you encounter a Port in Use error. (5079284)

Close the first instance of the application before you launch the second instance of the application.

In the BlackBerry Smartphone Simulator, when you start a second instance of the web browser, you encounter an error. (5079276)

None.

On a computer running Windows 7, if you have the BlackBerry Smartphone Simulator and the BlackBerry Java Plug-in for Eclipse installed, at times the simulator may not be located. (5079428)

Restart Eclipse and the BlackBerry Smartphone Simulator.

When you configure an SD Card image with a path that includes a space, you cannot use the BlackBerry Smartphone Simulator launch configuration.

You must enclose the path in quotation marks (").

Code signing

Issue

Workaround

The BlackBerry Signing Authority Tool is not available for computers that run Mac OS. (5079465)

Install the BlackBerry Signing Authority Tool on a Windows computer and communicate with it over TCP/IP to request a key pair by using the BlackBerry Signature Tool.

Windows only. If you import the Persistent Store Demo sample app and then package and sign the app, a warning that signing is required persists. (5079366)

Delete the warnings in the Problems view first, and then sign the app.

When you package a BlackBerry application project that requires signing, after you sign the application once, you are not prompted for a signature again until repackaging is required. When you run the same application, you are always prompted for a signature. (5079331)

None.

Workspaces and projects

Issue

Workaround

Windows only. When you install the BlackBerry Java Plug-in for Eclipse, if you specify a very long installation path name or workspace path name, you encounter errors when you try to import sample applications. (5079375)

Make the installation and/or workspace path name less than 128 characters.

If you create a project using the New BlackBerry Project Wizard and select the Create Project from existing source option, the dependent libraries are not available and you receive compile errors in the Problem view. (5079466)

Use the Import / Existing Projects into Workspace option instead.

When you get a restart dialog because the preprocessor is being configured, the preprocessor hook could not be configured correctly dialog appears. (5079460)

The Eclipse environment may not be configured correctly. Reinstall the BlackBerry Java Plug-in for Eclipse using the full installer, and install it to a new path.

You cannot build a project once to run on multiple versions of the BlackBerry Device Software. (5079342)

For each version of the BlackBerry Device Software on which you want your app to run, complete the following steps:

  1. In the project Properties, specify the JRE (for example, BlackBerry JRE 7.1.0).
  2. In the BlackBerry Application Descriptor, on the Build tab, change the Output folder and set the Preprocessor Directives.
  3. Build your app.

When you create a BlackBerry application project that depends on a Java project, you may not be able to package the application or load it on a BlackBerry device. (5079439)

You can use either of the following methods:
  1. Create the dependent project as a BlackBerry library project rather than as a Java project and deploy it separately on a BlackBerry device.
  2. Build your Java project as a separate library (JAR file) and include it in the .COD file of the BlackBerry project by adding the JAR file to the Java build path and exporting the JAR file.

When you add a BlackBerry application project as a dependency to a Java project, you encounter an error. (5079290)

Use a BlackBerry project of the library type instead.

After a user upgrades to a newer version of a BlackBerry device application, a duplicate entry for the application exists in Options > Applications, but only one version is accessible from the Home screen. (5079271)

Build the .alx and .jad files to generate the same Application ID when the application is installed on a BlackBerry device.

Localization

Issue

Workaround

Windows only. When you delete an .rrh resource file from a BlackBerry application project, after you rebuild the project by using Project > Clean and then package the project, you encounter a compilation error. (5079372)

Restore the .rrh resource file, or create a new BlackBerry resource file rrh/.rrc pair.

Mac OS only. On a computer running Mac OS X 10.6 (Snow Leopard), in Eclipse, after you make changes to a resource file in the Resource Editor, when you click Validate the console does not display any output. (5079371)

None.

When you hotswap your BlackBerry application, if you delete locale resources an illegalArgumentException is thrown. (5079361)

Delete and redeploy the app.

When you use a version of Windows that is not English, when you import a BlackBerry device project that contains locale resources, a pound currency symbol (£) is appended to the file name of the .crb file that is created in the /bin folder of the project. (5079328)

Use an English version of Windows, or in Windows, configure the Regional and Language Options to change the language for non-Unicode programs to English.

Unclassified

Issue

Workaround

When you attempt to save profile data as an XML file, you may receive an error. An empty XML file is created. (5079395)

Save the profile data as a .csv file instead.

Mac OS only. On a computer running Mac OS X, when you install the BlackBerry Java Plug-in for Eclipse, if you specify a very long installation path name or workspace path name, when you run an application on a BlackBerry smartphone, the application fails to load and no error dialog or prompts are displayed. (5079376)

Make the installation and/or workspace path name less than 128 characters.

Windows only. When only the plug-in is installed, the Microsoft Redistribution package SP1 is not recognized. (5079462)

Install the base VC++2008 Redistributable package from http://www.microsoft.com/.

Windows only. When you run the CommunicationAPIDemo sample application for the BlackBerry Java SDK 7.0 or 7.1, an error occurs. (5079456)

Add the path for the JDK bin folder (%JAVA_HOME%\bin) to the PATH environment variable of your system.

Using the PersistentStoreDemo project, if you run the app on the BlackBerry Smartphone Simulator and create and save a meeting, and then (without closing the simulator) change a meeting class, and then build and run the app on the BlackBerry Smartphone Simulator again, the first meeting still exists. That is, you cannot hot-swap an app that altered objects with persisted fields. (5079447)

Close the previous debug session and restart the BlackBerry Smartphone Simulator when changing objects with persisted fields.

When you specify the version number of a MIDlet application on the BlackBerry Application Descriptor screen for a BlackBerry project, if you type spaces or special characters in the Version field, the characters are accepted but do not generate an error. (5079441)

Use a version definition that complies with the MIDlet specification by using three numeric segments, for example 1.2.3.

In the BlackBerry Application Perspective, if you select text in the Eclipse editor while Convert String to Hex is enabled, when you change to another perspective, the conversion fails. (5079298)

None.