This document describes the bugs known to exist in the Openwave® SDK 6.x that are considered to be most important
to application developers. If you discover a bug not listed here, please report the bug to
our Developer Support Team.
SDK 6.2
If you do not use the -clearcache argument when you change gateways with the -g argument, the -sethome argument may have no effect. Restarting the SDK with the -clearcache argument should correct this problem.
HTTP errors are recorded in the Phone Information window and in the log file as Request status: 200, regardless of the nature of the error.
If you do not use the -clearcache argument when you change gateways with the -g argument, the SDK can fail to connect to the gateway due to a secure key-exchange problem. Restarting the SDK with the -clearcache argument should correct this problem. If not, exit the SDK, delete the C:\Program Files\Openwave\SDK 6.2\program\wap\.wapconfig file, set your key state on the MAG to Force, and restart the SDK.
The Browser sometimes takes more time than expected to open an MMS message; during this time, the display area of the simulator may not be drawn correctly.
When viewing a page whose time to live (TTL) has expired, navigating back will remove the page from the history stack. This means you can't navigate forward to that page.
When changing configuration files using the simulator's File > Change Device command, sometimes the SDK simply exits.
If an MMS message has a background sound, the browser keeps playing it if you open another message that has a sound.
The Network Information window is not available in the WAP Simulator Plug-In.
The Control-C shortcut for the Network Information window's Edit > Copy command does not work in the HTTP Simulator.
In the HTTP Simulator, HTTPS transactions are not displayed in the Network Information window.
SDK 6.1
If you do not use the -clearcache argument when you change gateways with the
-g argument, the -sethome argument may have no effect. Restarting the SDK with the
-clearcache argument should correct this problem.
HTTP errors are recorded in the Phone Information window and in the log file as
Request status: 200, regardless of the nature of the error.
