Known issues

This section lists known issues for the BlackBerry Java Plug-in for Eclipse v1.5 for Windows.

Installation

Issue

Workaround

Check for updates dialog does not show up. (2079813)

None.

The license agreement for the BlackBerry Java Plug-in for Eclipse 1.5 do not display the correct copyright period and text. (2114755)

None.

When you install the BlackBerry Java Plug-in for Eclipse by using the BlackBerry update site, if the .../configuration/config.ini file is not writeable by the Eclipse osgi.framework or by Eclipse Pulsar, a preprocessor hook loop is created. (578783)

Workaround 1: Edit the .../configuration/config.ini file to add or append the following text: osgi.framework.extensions=[<other-ref>,]reference\:file\:net.rim.ejde.preprocessing.hook_1.1.2.<date-ver>.jar (as installed, for example, :net.rim.ejde.preprocessing.hook_1.1.2.201003212304-12.jar).

Workaround 2: Edit the eclipse.ini file to add or append the following text: -Dosgi.framework.extensions=[<other-plug-in>,]net.rim.ejde. Use this workaround for Eclipse Pulsar.

Debugging

Issue

Workaround

When you debug a BlackBerry application project on the BlackBerry Smartphone Simulator you encounter a connection timeout. (2018622)

Increase the amount of system RAM to 4 GB.

On a computer running Windows 7 (64-bit), when you debug a BlackBerry application project on the BlackBerry Smartphone Simulator, the launch progress stops at 31% and the simulator does not start. (1162452)

Restart the computer.

When you debug a BlackBerry 7.1 application project that depends on a Java project, when the debugger stops at a breakpoint, if you click on an array object in Variable view, an "Exception processing async thread" error occurs. (2402629)

None.

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. (2077702)

None.

The simulator crashes when you relaunch the disconnected RIM JVM. (2085777)

Re-launch through the launch configuration.

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. (1131217)

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

In Eclipse, when you select a variable in the detail pane, the detail formatter issues an error message. (1036094)

None.

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

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

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. (762467)

Close the application before hot-swapping.

When you debug your BlackBerry device application by hot-swapping, if you remove a field from a persistent instance, when you relaunch your application, hot-swap does not stop. (743487)

None.

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 does not reflect the devices that are currently attached even after selecting the option to refresh the list. (535402)

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

If you create two BlackBerry launch configurations, the BlackBerry Java Plug-in for Eclipse does not prevent you from launching both sessions. Both sessions might not start. (534772)

Do not start multiple debug sessions.

If you have two BlackBerry application projects that contain Java files with the same name, when you debug the project, the BlackBerry Java Plug-in for Eclipse might open the wrong source file. (298096, 518682).

On the Debug Configurations > Source tab, select Search for duplicate source files on the path and rename any files with duplicate names.

When you debug a BlackBerry device application, the BlackBerry profiler view automatically closes when the debugger terminates. (354545).

None.

When you debug a BlackBerry device application by using Run > Debug as > Running BlackBerry Simulator, the application is not loaded automatically onto the BlackBerry Smartphone Simulator. (487482)

You must load the application manually onto the BlackBerry Smartphone Simulator.

When you protect a BlackBerry device application with a private key, the application is not signed automatically. (508277)

You must sign the application manually by using the BlackBerry Signing Authority Tool.

When you comment out a line of executable code that has a toggled break point, the break point is not removed. (559282)

None.

BlackBerry Smartphone Simulator

Issue

Workaround

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. (2502200)

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. (1996596)

Terminate the process manually.

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

Set the JAVA_HOME environment variable to the directory where you installed the Java SDK, 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, uninstall it.

If you are running Windows 7 (64-bit), after you debug your BlackBerry 7.0 application project on the BlackBerry Smartphone Simulator and then use BlackBerry > Clean Simulator to reset the simulator, the simulator files are not removed. (2024707)

None.

Description section is missing from application management. (1889308)

None.

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. (1112690)

Log in with System Administrator privileges when you install a BlackBerry Smartphone Simulator and when you use the BlackBerry Java Plug-in for Eclipse.

When you run your BlackBerry device application on the BlackBerry Smartphone Simulator, console output is interrupted with the string "[0.0]" at the beginning of each line at fixed intervals. (1055525)

None.

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. (1041335, 1041338)

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. (915337)

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. (760450)

None.

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 (").

When you use Windows 7, if you install an external BlackBerry Smartphone Simulator in the default folder c:\Program Files, the BlackBerry Java Plug-in for Eclipse does not recognize the BlackBerry Smartphone Simulator. (587797)

You should install an external BlackBerry Smartphone Simulator in the root of the disk drive in a folder that has a shorter name. You must give the folder read-write permissions. Note: You can protect all .jar and .exe files by giving them read-only permission.

Code signing

Issue

Workaround

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. (1113779)

None.

If you close Eclipse while the BlackBerry Signature Tool is running, you cannot clean or package your BlackBerry application project. (531342)

Close the signature tool manually.

Workspaces and projects

Issue

Workaround

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. (2606461)

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

When you create a project for a specific BlackBerry Java SDK, for example BlackBerry 7, if your project depends on a library for a different version of the BlackBerry Java SDK, for example BlackBerry, when you package the project, an error occurs. (1164128)

Build each dependency separately and then have the main project refer to the dependent project as a library in the class path. If necessary, export the dependent library when you deploy your project.

In the BlackBerry_App_Descriptor.xml file for your BlackBerry application project, on the Build tab, when you select the Convert image files to PNG option and then run the app in the BlackBerry Smartphone Simulator, the images are not converted to PNG format. (1049367)

None.

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. (1051705)

You can use either of the following methods:
  1. Create the dependent project as aBlackBerry 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 application 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. (1015170)

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. (725671)

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

When you run a BlackBerry application project, you might encounter application errors in the Eclipse workspace.

Do not use special characters in BlackBerry application project properties.

When you create a BlackBerry application project, if you use special characters (for example, @, $, %) in the project name, you might encounter an XML validation error. (374640)

Do not use special characters in BlackBerry application project names.

Localization

Issue

Workaround

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. (2406319)

Restore the .rrh resource file.

If you delete an application's language resource file while running the application in the BlackBerry Smartphone Simulator, after the simulator relaunches the application, the resource file is still present. (537426)

When you want to delete a resource file, in the simulator, close the application. Delete the resource file and then launch the application.

When you rename a BlackBerry device application package while an original locale file is open in the Resource Editor, the original locale file is copied, not moved. (368943).

Close the original locale file in the Resource Editor before you rename the package.

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. (494006)

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.

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

None.

Unclassified

Issue

Workaround

If you create a new BlackBerry 4.5 or 5.0 application project by using the HelloBlackBerry template, when you build the project, build errors occur. (2724703)

Create your project using a different template.

When you run a BlackBerry 4.5 application project on a BlackBerry smartphone, the appplication fails to load on the device and no error prompt or dialog is displayed. (2634479)

Install an additional BlackBerry Java SDK, for example 7.0.

When you define an installation path for the BlackBerry Java Plug-in for Eclipse that contains spaces, you encounter an "Invalid folder" error. (2606461)

Remove the spaces from the installation path.

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

Add the path for the JDK bin folder to the PATH environment variable of your system.

Exception processing async thread queue when debugging with watch Expression. (2084252)

Go to express view, remove "new" expressions like LabelField("BBLib_Hello"). Then resume the debug session.

When you click the Open Hello Contents from the toolbar, Topic not found is displayed. (2401133)

None.

A duplicated Getting Started Page link in the Main menu shows up in the BlackBerry Application Development perspective. (2309086)

None.

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

None.

When you import samples, the Select All and Deselect All .do not display correctly. (2437342)

None.

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. (1103499)

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

If you create a MIDlet name that is 255 characters long, when you enter the name in the Name of main MIDlet class field or in the Title field of an Alternate Entry Point (AEP) on the BlackBerry Application Descriptor screen, when you package your BlackBerry project, packaging fails. (1103724, 1103725)

Create MIDlet names that are shorter than 255 characters.

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. (1037354)

None.

When you save a linked contact, you encounter an UncaughtIllegalArgumentException. (743694)

None.

When you activate the Drag and Drop feature in the Resource Editor so that you can drag and drop keys into the source code window, the feature does not work. (369175)

None.

When you remove a BlackBerry Java SDK from a launch configuration, you encounter a NullPointerException and the launch configuration is corrupted or, when you update the BlackBerry Java SDK without changing the launch configuration, you are prompted to save unsaved changes. (560259)

None.

Next topic: Legal notice
Previous topic: Fixed issues

Was this information helpful? Send us your comments.