Known issues

This section lists known issues for the BlackBerry® Java® Plug-in for Eclipse®.

Installing

If you upgrade from the BlackBerry Java Plug-in for Eclipse beta 1.1.1.15 to 1.1.2 that includes the BlackBerry® Java® SDK 5.0, the BlackBerry Java Plug-in for Eclipse does not switch to the associated BlackBerry JRE™ automatically. (559291)

Impact: The new features of the BlackBerry Java SDK 5.0, such as improved hot-swap, are not available, and you cannot use the clean simulator feature in the previous BlackBerry JRE. This occurs when the Eclipse restart sequence updates both plug-ins. It does not occur when only the BlackBerry Java SDK is updated.

Workaround: Manually select the upgraded BlackBerry JRE by navigating to Windows > Preferences > Java > Installed JREs. Select the old BlackBerry JRE and click Edit. Change the Definition File by navigating to the newly installed BlackBerry JRE. In the ../plugins/net.rim.ejde.componentpack5.0.0_5.0.0.x/components/ folder, select the BlackBerry .ee file and click Finish.

If you want to install multiple versions of the BlackBerry® Java® SDK, you must specify your login credentials for each SDK. (545417)

Impact: You must log in every time you want to install an SDK.

Workaround: You can cache your password so that, after the first installation, you do not have to enter your credentials. In the login dialog box, select the check box.

When you install the BlackBerry Java Plug-in for Eclipse or a BlackBerry Java SDK in Eclipse 3.5.1, a warning about unsigned .jar files displays. (427122)

Impact: You must dismiss the warning every time you install a component.

Workaround: 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 Eclipse osgi.framework or by Eclipse Pulsar, a preprocessor hook loop is created. (578783)

Impact: You are continually prompted to configure and restart Eclipse.

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.

When you upgrade from the BlackBerry Java Plug-in for Eclipse 1.x to 1.1.2, signing keys are not transferred automatically. (579957)

Impact: You cannot sign BlackBerry device applications.

Workaround: You can install the keys manually by using Window > Preferences > BlackBerry Java Plug-in > Signature Tool > Import Existing Keys. Navigate to the location where the keys were previously installed (for example, /plugins/net.rim.ejde/signTool for the BlackBerry Java Plug-in for Eclipse 1.1.1).

Debugging

If you move the BlackBerry Java Plug-in for Eclipse to a new location, you cannot use the BlackBerry® Smartphone Simulator. (545814)

Impact: You cannot change the location of the BlackBerry Java Plug-in for Eclipse by moving or renaming the folder.

Workaround: Click Project > BlackBerry > Clean Simulator to clean the simulator then launch the simulator again.

If you start debugging a project with breakpoints and then change the BlackBerry JRE, the debugger does not provide output. (557517)

Impact: You cannot view debugging information.

Workaround: Restart Eclipse.

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)

Impact: You can attempt to attach a debugger to a specific device without selecting a device. You cannot refresh the list of available devices to attach to the debugger.

Workaround: 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)

Impact: You cannot run multiple debug sessions.

Workaround: 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 opens the wrong source file. (298096, 518682).

Impact: When you debug your application the wrong source file is opened.

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

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

Impact: You cannot view BlackBerry profiler information after the debugger terminates.

Workaround: None.

When you click Debug as > Running BlackBerry Simulator to invoke a debug session for a BlackBerry device application, the debugger does not terminate when the BlackBerry Smartphone Simulator terminates. (410786)

Impact: You must manually stop the debugger.

Workaround: 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)

Impact: The application is not loaded automatically onto the BlackBerry Smartphone Simulator.

Workaround: 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)

Impact: When you debug the application in the BlackBerry Smartphone Simulator you might encounter an error.

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

After you debug a BlackBerry device application in the BlackBerry Smartphone Simulator, if you run the application from Eclipse and then close the simulator, the simulator does not stop. (512588, 532712)

Impact: When you run or debug the next BlackBerry device application you encounter an error and you cannot clean the simulator.

Workaround: Restart Eclipse.

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

Impact: The debugger will suspend execution at the commented line.

Workaround: None.

BlackBerry Smartphone Simulator

When you try to configure the BlackBerry Smartphone Simulator to use a file media card, the simulator does not recognize the media card. (543853)

Impact: You cannot configure the BlackBerry Smartphone Simulator to use a file media card.

Workaround: You can configure a file media card when the BlackBerry Smartphone Simulator starts, or you can configure a file system media card by using a launch configuration.

When you try to clear files from a simulated media card in the file system by using the clean simulator feature, the media card is not cleared and no error is displayed. (543845)

Impact: You cannot clear a simulated media card by using the clean simulator feature.

Workaround: You must manually delete the folder.

If you configure a simulator media card and, in the SD Card Image field, you specify a path that includes a space, an error occurs indicating that there is an unrecognized argument.(543816)

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

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

When the BlackBerry Smartphone Simulator is running and you create a new run configuration that uses a different BlackBerry JRE™ or simulator/device, the BlackBerry Java Plug-in for Eclipse prompts you to close the simulator that is currently running. If you close the simulator manually and then try to dismiss the prompt, the new simulator launch configuration does not start. (543775)

Impact: When the BlackBerry Smartphone Simulator is running, you cannot run a new launch configuration that uses a different BlackBerry JRE or simulator/device.

Workaround: Do not close the simulator manually. Allow Eclipse to close the simulator.

When you run a MIDlet on the BlackBerry Smartphone Simulator and then make a change to the application, when you reload the application on the simulator, the change is not reflected on the simulator display and you encounter an exception when you close the application. (560007)

Impact: You cannot change the MIDlet and then reload it while the application is running on the simulator.

Workaround: Close the MIDlet application before you reload it on the simulator.

If you are using a 64-bit operating system, you cannot close a BlackBerry Smartphone Simulator that you launched outside the BlackBerry Java Plug-in for Eclipse. (565499)

Impact: You cannot close the BlackBerry Smartphone Simulator.

Workaround: You must install FledgeHook.exe, a process monitoring program that can help close the BlackBerry Smartphone Simulator when the 'x' button is pressed. You can run FledgeHook.exe manually or as part of a batch (.bat) file that you use to start the BlackBerry Smartphone Simulator. You can find FledgeHook.exe in <Eclipse-install>/plugins/net.rim.ejde/vmTools. Note: 64-bit operating systems require 32-bit Java 1.6 and 32-bit Eclipse 3.5.x.

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)

Impact: You cannot clean a BlackBerry Smartphone Simulator that is installed in the C:\Program Files folder.

Workaround: 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

If you configure your BlackBerry application project to automatically sign .cod files after packaging, when you run or debug the application, the BlackBerry® Signature Tool signs keys that are marked as optional. (533697)

Impact: Some .cod files are unnecessarily signed.

Workaround: None

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

Impact: You cannot clean and package a project.

Workaround: Close the signature tool manually.

If you remove a .key file from a BlackBerry application project, the associated entries in the BlackBerry_App_Descriptor.xml file are not removed. (528274)

Impact: After removing a .key file from a project, you receive an I/O error when you package the project.

Workaround: Using a text editor, manually remove references to the .key file from the BlackBerry_App_Descriptor.xml file.

When you run a BlackBerry device application on a secure device, if the application does not require signing, the BlackBerry Signature Tool prompts for signing. (467422)

Workaround: None.

Code signing warnings are displayed in the editor even when signing is not required. (490787)

Impact: Unnecessary code signing warnings are displayed.

Workaround: None.

When your workspace in the BlackBerry Java Plug-in for Eclipse contains a mix of projects that are defined for different BlackBerry JREs (from BlackBerry Java SDKs), after you import and package a project for a JRE, when you import and package another project for a different JRE, the BlackBerry Signature Tool might not run. (605460)

Impact: The .cod file might not be signed.

Workaround: You can clean the project, sign the .cod file manually, or restart Eclipse.

Workspaces and projects

When you use Windows® 7 with Eclipse 3.5.0 or 3.5.1, if you change the BlackBerry_App_Descriptor to remove a resource file that is marked as invalid (for example, if you changed the file externally) from the Application Icons section, you might encounter a stack overflow error. (601594)

Impact: After you dismiss the error dialog, Eclipse exits and you must restart Eclipse.

Workaround: Upgrade to Eclipse 3.5.2.

You can create two identical preprocessors in the BlackBerry_App_Descriptor.xml. (538991)

Impact: You can create a project descriptor with two identical preprocessors when you should not be able to.

Workaround: Avoid creating two identical preprocessors, or you can delete or ignore the duplicate.

If you try to clean a project more than once immediately after packaging, it might not complete successfully. (537756)

Impact: You might not be able to clean the project.

Workaround: None.

When you create a BlackBerry application project that is a library and run the library application on the BlackBerry Smartphone Simulator, the library application has an associated default icon. (520519)

Impact: Library applications appear with a default icon on the simulator when they should not have an icon.

Workaround: Using a text editor, in the BlackBerry_App_Descriptor.xml file, configure IsSystemModule to true, or you can ignore the icon.

When you specify the properties for a BlackBerry device application project, some fields might accept special characters (for example, @, $, %) that are not valid in the Eclipse development environment. (242681).

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

Workaround: Do not use special characters in 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)

Impact: You encounter an XML validation error when you run your application.

Workaround: Do not use special characters in project names.

When you import a BlackBerry application project by linking the files rather than by copying the files, and you share the project using the Perforce® plug-in for Eclipse, when you synchronize the project, you encounter an error. (476444)

Impact: You are unable to synchronize your project.

Workaround: If the files are not in the Eclipse workspace, you can synchronize the files referenced by the link outside of Eclipse.

When you update the BlackBerry Java Plug-in for Eclipse from version 1.1.1 to 1.1.2 and you launch a project that you created in version 1.1.1, the default JRE in the workspace or in the project is not updated. (560511)

Impact: You cannot access the updated JRE in an application project that you created in the BlackBerry Java Plug-in for Eclipse 1.1.1.

Workaround: Manually change the default JRE in Preferences > Installed JREs by editing the JRE to select the .ee file from the BlackBerry Java Plug-in for Eclipse 1.1.2.

When you use the Import Existing Projects wizard to import by linking a project that was created by using the BlackBerry® JDE Plug-in for Eclipse 1.0, when you build the project, you might encounter an exception that a .preprocessed folder already exists. (538764)

Impact: You might encounter an exception when you compile the project.

Workaround: You must disable the Build Automatically option in Eclipse and refresh the project before building it.

The following properties in the BlackBerry_App_descriptor.xml file do not correlate with the application type. (520325)
  • Icons for Library type applications (if present before the switch) should be unavailable and not passed to RAPC.
  • Warnings for main(String[]) missing is valid only for the BlackBerry Application (CLDC) type.
  • Alias list makes sense only for Libraries, so it should be unavailable for other application types.
  • Auto-run on startup for Library applications makes sense if there is a libMain(String[]).

Impact: Certain project properties do not correlate with the application type.

Workaround: You must correlate the properties manually.

Localization

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)

Impact: If you delete an application's language resource file while the application is running, after you relaunch the application, the BlackBerry Smartphone Simulator displays the deleted resource.

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

If you create a CLDC application that has a library dependency and the library has language resource files, you cannot set the Resource Title ID in the application project properties. (522311)

Impact: You cannot use the resource files from a dependent library in your project.

Workaround: None

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

Impact: You might have two copies of the original locale file.

Workaround: 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)

Impact: You cannot compile the BlackBerry application project.

Workaround: 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 specify a Description ID for a locale resource in the BlackBerry_App_Descriptor.xml file of your BlackBerry application project, the description does not display if you build your application with BlackBerry Java SDK 5.0. (506631).

Impact: When you run the BlackBerry device application in the BlackBerry Smartphone Simulator, 'Unavailable' appears in the description field in Options > Applications > Core > <application name>.

Workaround: None.

Unclassified

When you create a launch configuration and you change the default JRE, the description from the new project BlackBerry JRE is not updated in the Runtime JRE dialog. (557094)

Impact: You do not see the correct runtime JRE description.

Workaround: Click on a different tab and then go back to the JRE tab.

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

Impact: You are not able to drag and drop keys into the source code window.

Workaround: None.

When you develop a BlackBerry device application using BlackBerry Java SDK 4.7, 4.6.x, or 4.5, Eclipse might exit when you hover the mouse over certain classes or methods (such as PersistentContent.addListener) to view the related Javadoc™ description. (501375, 565695, 566182)

Impact: You might not be able to view all Javadoc descriptions from within Eclipse.

Workaround: 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)

Impact: You cannot remove or update the BlackBerry Java SDK in an existing launch configuration.

Workaround: None.

If there are no preprocessor directives defined in your BlackBerry application project, the Select All and Deselect All options are still available. (560344)

Impact: The selection options should not be available if there are no preprocessor directives defined.

Workaround: None. This behavior does not create any issues.

When you import an .epf file that you created in the BlackBerry Java Plug-in for Eclipse 1.1.1 into the BlackBerry Java Plug-in for Eclipse 1.1.2, the import fails. (518912 )

Impact: You cannot import the .epf file from the BlackBerry Java Plug-in for Eclipse 1.1.1.

Workaround: None.


Was this information helpful? Send us your comments.