Provides troubleshooting information about generating device application code in the Device Application Designer.
Problem: Cannot deploy the device application to the BlackBerry Simulator.
Solution 1: Verify that the BlackBerry Simulator MDS is running. Start it, if necessary.
For example, do not use %Java_Home% or %SystemRoot%. Replace any % symbols with the full path.
Problem: When compiling code for a BlackBerry application that contains a custom action, you receive this error: The constructor ScreenAction(IBOBScreen, boolean, null) is undefined.
Solution: In Sybase Unwired Platform 1.5.5, the constructor ScreenAction(IBOBScreen screen, boolean closeCurrentScreen, String[] relationships) has been removed.
ScreenAction(IBOBScreen screen) ScreenAction(IBOBScreen screen, boolean closeCurrentScreen) ScreenAction(IBOBScreen screen, boolean closeCurrentScreen, boolean showLoadingScreen) ScreenAction(IBOBScreen screen, boolean closeCurrentScreen, IExecutorCommand backgroudRunnable, String loadingMsg)
Problem: A connection profile appears in Windows Mobile generated code instead of a login screen.
Explanation: It is likely that a login screen was not included in the screen flow design. Device applications require a login.
Solution: If no login screen is included, a connection profile screen appears so the user can enter login credentials. The user can enter the password and click OK, but a better solution is to redesign the screen flow for Windows Mobile to include a login screen.