Known issues

This section lists known issues for the BlackBerry® Java® SDK 7.0 MR, Bundle 63.

Installation and setup

When installing the BlackBerry Java SDK on Windows® 7, a UserAccessControl window is opened requiring an administrator password. (2005941)

Impact: You cannot update the jad.exe file without an administrator password.

Workaround: None.

BlackBerry APIs

The following method in the net.rim.device.api.openvg.VGUtils class does not list parameter names in the auto-complete drop-down list: (1247821)

  • vgImageSubData(VG vg, Bitmap bitmap, int offsetX, int offsetY, boolean flipY, int image, int x, int y, int width, int height)

Impact: The methods are not consistent. You must enter this method manually.

Workaround: None.

BlackBerry Smartphone Simulator

The BlackBerry Smartphone Simulator displays the message "SocketException file cannot be deleted" when restarted. (1891173)

Impact: You cannot restart the BlackBerry Smartphone Simulator by selecting Debug > Restart.

Workaround: Close and reopen the BlackBerry Smartphone Simulator.

When attempting to simulate NFC functionality on the BlackBerry Smartphone Simulator , if you do not connect the elements in the right order, it will fail to connect to the NFC Simulator, and present a number of error messages. (1517026)

Impact: You will need to restart all NFC-related processes (The Connection Center, The NFC Simulator, Open NFC Core Edition 4.2.3, and the BlackBerry Smartphone Simulator) to proceed.

Workaround: To simulate NFC without errors, do the following:

  1. Open the Connection Center
  2. Open the NFC Simulator
  3. If the Trace Server did not automatically start, open the Trace Server.
  4. In the Connection Center, click the Services List button.
  5. In the Services List window, under the NFC Controller header, right-click NFC Device #1 and select Copy service URI from the drop-down menu.
  6. If launching the simulator from the BlackBerry JDE do the following:
    1. In the BlackBerry JDE, navigate to Edit > Preferences.
    2. On the Simulator tab, select the Advanced tab.
    3. In the Command Line text area, add the following parameter: /nfcc-uri=""the URI copied in step 4"".
    4. Press OK, and launch the BlackBerry Smartphone Simulator.
  7. If launching the simulator from its .bat file, do the following:
    1. Find the .bat file for the simulator you want to boot, and open it in a text editor.
    2. Add the parameter /nfcc-uri=""the URI copied in step 4"".
    3. Save the .bat file.
    4. Run the .bat file.

The BlackBerry Smartphone Simulator cannot simulate a USB connection on Windows® 7. (1393036)

Impact: You cannot use the USB Cable Connected option to load a .cod file or take a screen shot on Windows® 7.

Workaround: None.

BlackBerry Integrated Development Environment

The title field of an application project is not reflected when the project is built. (1995417)

Impact: Instead of the title listed in the title field, the application's title is the project name.

Workaround: None.

In the BlackBerry® Java® Plug-in for Eclipse®, a runtime error appears when closing the BlackBerry Smartphone Simulator. (1882544)

Impact: The BlackBerry Smartphone Simulator closes with errors.

Workaround: None.

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.

When you run a dir command an Error while building project error is displayed. (2024579)

Impact: You cannot run the dir command.

Workaround: None.

Debugging

When using Javaloader does not update the CodeModuleGroups. (2081716)

Impact:The BlackBerry Smartphone Simulator stops responding.

Workaround: None.

Sample applications

Using the "Submit" button, and the "Change Search" menu item causes errors in the Browser Field 2 sample application. (2000587)

Impact: The application may present you with an error message or the web search results may not be displayed.

Workaround: Close and restart the application, or press Submit twice to view the web search results.

The HTTP Push Demo sample application does not work with the "pap" option. (1938559)

Impact: You cannot use the sample application's "pap" option.

Workaround: None.

The Buffered Playback sample application throws a file system error when trying to load a .wav file (1632360)

Impact: You cannot play .wav files.

Workaround: None.

The Table and List sample application does not display the Tree Screen table correctly. (1624288)

Workaround: None.

When you select Go To A Location in the MapField Demo, no location information is displayed at the bottom of the screen. (2019042)

Workaround: None.

When using the SVG Forms Demo the cursor is positioned incorrectly. (2018274)

Workaround: None.

The screen orientation does not change when using the Tilt Demo sample application with the default settings. (2080431)

Impact: You cannot use the Tilt Demo sample application.

Workaround: Only enable West and East orientation changes; disable North in the options.

The PhoneLogs API Demo throws an IllegalStateException when you edit. the Participants field and click Save. (2072595)

Workaround: None.

The Enhanced Map Field sample application throws a java.lang.IllegalArgumentException when run. (2072638)

Impact: You cannot run the Enhanced Map Field sample application.

Workaround: None.

When using the File Explorer Demo, clicking the trackpad results in two consecutive selections. (2079807)

Impact: You not only select the option you want on the first menu, but you also select the option on the second menu.

Workaround: Press the Return button once to go up one level.

When you select InvokeDefault in the BlackBerryMaps Demo application and click View Map the default map is displayed instead of the expected map. (1899510)

Workaround: None.

Next topic: Legal notice
Previous topic: Fixed issues

Was this information helpful? Send us your comments.