If you have Java 6 installed and you upgrade your Mac OSX to 10.9 Mavericks, the upgrade uninstalls Java 6. When you launch Momentics IDE, you are prompted to install Java 6. However, if you have Java 7 installed, you get an error message that there is a missing CreateJavaVM symbol and Momentics fails to launch.
Workaround: Uninstall Java 7 and relaunch Momentics IDE. You can reinstall Java 7 after the Java 6 install has completed.
On Linux systems, if the launch command contains "..", the Native SDK installer fails.
You might get a warning after uninstalling the Native SDK that some directories couldn't be removed. This can be ignored.
When you perform a software update, you must accept the security warning about installing unsigned software, and continue the installation.
In the bar-descriptor file, the <action> element used in previous versions of the Native SDK has been changed to be used with the Invocation Framework. The <permission> element has been reinstated for use to control permissions for an application. If you need to add permissions to your <action> application, you must change it to use the <permission> element. For more information, see The application descriptor file DTD.
During debug sessions, watchpoints are not supported.
If you get the message 'error in opening zip file' while updating or downloading the Momentics IDE or API Levels, you may need to clear your download cache.
Workaround: Remove <full_path_to_IDE_install>/p2/org.eclipse.equinox.p2.core/cache/*
If you set up a new simulator in the Device Manager, then click to pair a simulator downloaded from another source, in the Select .vmx file browser, you can't open the Momentics .app folder.
Workaround: With the folder browser open, press CMD+SHIFT+G and enter the path to the simulator folder.
On Mac OSX, While performing postmortem debugging in the IDE, the error message <symbol is not available> is shown in the debug trace.
Workaround: Before you can debug your app, you need to define the version of the runtime matching the device from where the core file was generated, manually install the runtime using the sdkinstall command line utility, and then add the shared libraries.
- From the command line in the IDE install directory, for Windows run sdkinstall.bat --install --runtime <runtime_version> or, for Mac or Linux run ./sdkinstall --install --runtime <runtime_version>. The runtime version is in the format of XX_X_X_XXXX, for example 10.2.0.1765.
- Restart the IDE so that the IDE discovers the newly installed runtime.
- Open the launch configuration for your app and click the Debugger tab.
- Click the Shared Libraries tab.
- Add the directories that you want. For example, add '<full_path_to_IDE_install>\runtime_XX_X_X_XXXX\qnx6\armle-v7\lib', '<full_path_to_IDE_install>\runtime_XX_X_X_XXXX\qnx6\armle-v7\usr\lib', and '<full_path_to_IDE_install>\runtime_XX_X_X_XXXX\qnx6\armle-v7\usr\lib\qt4\lib'.
- Click Debug.
In the Momentics IDE, if you open a new workbench window using Window > New Window and then close the original window, the new main toolbar is missing even if you restart the Momentics IDE.
Workaround: In your workspace, remove the file .metadata/.plugins/org.eclipse.e4.workbench/workbench.xml.
If your device is asleep and you attempt to attach using the BlackBerry Attach to running Application launch configuration, once the process is attached and you click Resume, the Resume button is disabled.
Workaround: Make sure your device is awake before attaching.
The application binary interfaces for the Dinkum C++ and GNU C++ libraries are incompatible. If you link an app against both libraries, you'll get a segmentation fault.
In the 10.1 version of the IDE, if you clear the check box Update IDE while installing the 10.2 SDK, you must update the IDE separately by clicking Help > Check for Updates. For compatibility, the 10.2 version of the SDK requires the 10.2 version of the IDE.
On Windows XP, if you install the Native SDK as an administrator using the default installation settings, and then log on as a non-administrator and start the IDE, you receive an error indicating that you cannot access the Native SDK.
When you switch between a device and a simulator, you must click Run instead of Build the first time after the switch.
If your application requires permissions and you launch it from the Momentics IDE, you must promptly accept the permissions on the device or the launch might time out.
If you rename an existing project, the IDE does not prevent you from using special characters, spaces, or other invalid naming conventions.
Workaround: To prevent issues, you should avoid using special characters, spaces, and names that are shorter than 3 characters or longer than 25 characters.
If you update the IP address of a BlackBerry Target and click OK without clicking Apply first, the IDE gives an error that it can't connect to the target. However, the IDE does connect.
Workaround: After updating the IP address, click Apply before clicking OK.
The locked SDKs in the Update Native SDK wizard may not accurately reflect the SDKs you are using. Use care when uninstalling SDKs to ensure that you don't uninstall an SDK that you want to continue using.
When you debug C programs, global variables do not appear in the Variables view.
Workaround: Type an expression in the Expressions view for each global variable that you want to inspect.
In a Linux environment, if you run the update manager and do not choose the options to switch to the newest SDK or to update the IDE, after the upgrade, the newest SDK is used by default.
Workaround: When you run the update manager, choose the option to update the IDE.
Cancelling the BAR file signing process deletes a previously signed BAR file.
Workaround: Increment the app version before signing the BAR file for the second time.
Postmortem debug is not available for shared libraries. The error message, "'Asynchronous viewer input update' has encountered a problem. An internal error has occurred." is displayed.
On Windows, using blackberry-deploy from the command line results in the error "Cannot connect: Permission denied: connect. Please check IP address settings for the target. Try to ping the target."
Workaround: Before you run blackberry-deploy from the command line, execute bbndk-env.bat, which sets the environment variables properly.
If you debug an application with Windows XP, you may receive an error stating there was an "InvocationTargetException".
Workaround: Install the Microsoft Visual C++ 2008 Redistributable Package (x86).
If you try to launch an application in debug mode that is already running on the device, the Momentics IDE may consume 100% of your CPU.
Workaround: Close the application on the device before launching it again.
When you create a project with a name that begins with a numeric value, you will see the following error: "Package ID is invalid". Project names cannot start with a numeric value and must start with a letter from a-z or A-Z.
If you launch Run Config and enable the Code Coverage tool, when you check Code Coverage Sessions, there is no coverage of shared and static libraries.
Do not launch your application with the Application Profiler enabled in debug mode. This might cause the IDE to stop responding.
If you use the Application Profiler with the Sampling method on a target, all threads must be bound to CPU 0 because the Application Profiler only checks samples for CPU 0.
Breakpoints that you set from .gdbinit are not visible in the UI of the IDE.
When debugging an OpenGL 2.0 project, the debugger may skip some breakpoints.
A class containing a pure virtual function using variable arguments cannot be inherited virtually. The following error is generated: "generic trunk code fails for method 'virtual void Log::Logger::Debug(const char*, ...)' which uses '...'".
During initialization, the MSYS.dll provided with the Native SDK will try to map network shares. If they are not available, then it will take as long as the network access timeout for each such mapped share for MSYS to start. This can lead to build times being slower if MSYS based utilities are used.
The Native SDK ships static libraries for most of the libraries of the platform. However, we recommend using shared libraries where possible to reduce your application footprint and to take advantage of bug fixes in the platform.