Known issues

This section lists known issues for BlackBerry® Java® SDK 6.0 MR bundle 70.

BlackBerry APIs

The RSSChannelImage class does not support the <link> element. (806868)

Impact: You cannot use the <link> element with the RSS Parser API.

Workaround: None

If you try to load web content in a BrowserField using a ButtonField, an IllegalStateException with the message "tried to remove FieldWithFocus" is thrown. (732844)

Impact: You cannot load web content in a BrowserField using a ButtonField.

Workaround: None

BlackBerry Integrated Development Environment

The prerequisites screen for the BlackBerry Java SDK installer displays the incorrect URL from where to download the Java® Platform, Standard Edition Development Kit (JDK®). (1027163)

Impact: You are directed to an incorrect URL for the JDK.

Workaround: You can download the JDK from www.oracle.com.

The BlackBerry JDE Components 6.0.0 is listed incorrectly in the Control Panel. (763026)

Impact: In the Control Panel, BlackBerry JDE Components 6.0.0 is listed as BlackBerry JDE 6.0.0.

Workaround: None

The installer screen for the BlackBerry JDE Component Package 6.0.0 specifies an incorrect directory for the default installation. (751417)

Impact: The BlackBerry JDE components might be installed in the incorrect directory.

Workaround: Change the default directory to C:\Program Files\Research In Motion\BlackBerry JDE Component Package 6.0.0.

When you attach the debugger to a BlackBerry device, a message appears with a list of missing debug files. When you try to debug an application, the class types for local instances of BlackBerry API classes are listed as "unknown". (528229)

Workaround: Click Cancel in each dialog.

BlackBerry Smartphone Simulator

The BlackBerry Email Simulator does not forward emails to or from the BlackBerry Smartphone Simulator . (1037827)

Impact: You cannot forward email messages to or from the BlackBerry Smartphone Simulator.

Workaround: None

When you search for an application from the Home screen of the BlackBerry device, and then change the focus to the application, the rollover image for the application icon does not change. (1036329, 1037542)

Impact: The correct rollover image does not display when the focus for the application icon changes.

Workaround: None

When you restart the BlackBerry Smartphone Simulator after correcting a compilation error in your application code, the application throws a RuntimeException. (1036058)

Impact: You cannot use the hot swap feature to restart the BlackBerry Smartphone Simulator after you corrected a compilation error.

Workaround: Click Debug > Go in the BlackBerry Integrated Development Environment after changing your code.

When you update the CodeModuleGroup by using the JavaLoader tool, the BlackBerry Smartphone Simulator closes. (1027944)

Workaround: None

If you use the JavaLoader tool to update modules on the BlackBerry Smartphone Simulator, the modules are not updated correctly. (1027896)

Impact: The modules on the simulator are not updated correctly.

Workaround: None

If you use the JavaLoader tool to remove files from the BlackBerry Smartphone Simulator, the files are not removed and you might receive the message "javaloader: Error: module is in use". (1027802)

Impact: You cannot remove files by using the JavaLoader tool.

Workaround: None

The BlackBerry® MDS Simulator does not support push functionality. (835944)

Impact: You cannot simulate push functionality.

Workaround: None

If you change resource values in an application, and then restart the BlackBerry Smartphone Simulator by clicking Debug > Restart, the application does not reflect the changes. (773921)

Impact: You cannot use the hot swap feature if you change resource values in an application.

Workaround: Click Debug > Go in the BlackBerry IDE after changing your code.

If you add or remove a class variable in a screen, the BlackBerry Smartphone Simulator might crash if you click Debug > Restart. (760199)

Impact: You cannot use the hot swap feature if you add or remove a class variable in a screen.

Workaround: Click Debug > Go in the BlackBerry IDE after changing your code.

The hot swap feature might fail to stop if you remove a field from a persistent instance. (743487)

Impact: You cannot use the hot swap feature if you remove a field from a persistent instance.

Workaround: Click Debug > Go in the BlackBerry IDE after changing your code.

If you make changes to a UI component and then restart the BlackBerry Smartphone Simulator by clicking Debug > Restart, you might receive an error with the message: "Please restart simulator: Private data members changed." (705863)

Impact: You cannot use the hot swap feature if you make changes to UI components.

Workaround: Click Debug > Go in the BlackBerry IDE after changing your code.

The BlackBerry® Messenger does not appear in the Instant Messaging folder. (665184)

Workaround: Open the application from the Home screen.

You cannot run two applications that use the BlackBerry® Browser engine (for example, the browser and a BlackBerry® WebWorks™ application) at the same time on the BlackBerry Smartphone Simulator.

Workaround: Click Cancel in each dialog.

Sample applications

The HTTP Push Demo sample application sometimes crashes and displays the message: " HTTPPushDemo is not responding; process terminated" when you try to launch the application from the Home screen of the BlackBerry device. (1038816)

Impact: You cannot run the sample application.

Workaround: Modify the sample application code so that in each catch (IOException) block where errorDialog() is invoked, insert a break statement after the errorDialog() statement.

The BrowserContentManager and BrowserField Demo sample applications throw an IOException, when you attempt to run the applications on a BlackBerry device. (1038809)

Impact: You cannot run the BrowserContentManager and BrowserField applications on a BlackBerry device.

Workaround: Make sure the radio for the BlackBerry device is turned on and that a SIM card is inserted in the device.

In the Table and List Demo sample application, when you select one of the following menu items: Rich List screen, Tree Screen or Table Adapter screen, the application throws a NullPointerException. (1037702)

Impact: You cannot choose a screen type from the application.

Workaround: None

In the Table and List Demo sample application, when you select Choose Style from the menu, the application throws an IllegalStateException. (1037666)

Impact: You cannot choose a table style from the application.

Workaround: None

In the UDP Demo sample application, when you successfully send a message to the server, a confirmation message does not display. (1037176)

Impact: You do not receive confirmation when messages were sent successfully to the server.

Workaround: Modify the sample application code for the line if(response.equals("RECEIVED"))and change equals to startsWith.

In the BlackBerry Maps Demo sample application, when you select InvokeDefault from the menu and then select View Map, the last map that you viewed does not display. (1036624)

Impact: The incorrect map displays.

Workaround: None

The OTA Sync Demo sample application does not synchronize the contacts to the BlackBerry device after you perform an enterprise activation. (763075)

Impact: You cannot synchronize contacts.

Workaround: None

The Location Picker Demo sample application cannot open a location saved as a Favorite location on devices with a touch screen. (746084)

Impact: If you selected the Do not stop execution when an exception is caught by "catch( Throwable )" check box on the Debugging tab of the Preferences screen of the BlackBerry IDE, a NullPointerException is thrown. Otherwise, no location is opened.

Workaround: Use the trackpad to make the selection instead of the touch screen.

The Media Engine Demo sample application is missing from the BlackBerry IDE. (628814)

Impact: You cannot use the sample application.

Workaround: Import the Media Engine Demo sample application from an earlier BlackBerry IDE release.

Next topic: Legal notice
Previous topic: Fixed issues

Was this information helpful? Send us your comments.