Search Tips   |   Advanced Search

Known limitations

General limitations apply to IBM MobileFirst Platform Foundation as detailed here. Limitations that apply to specific features are explained in the topics that describe these features.

In this documentation, we can find the description of IBM MobileFirst Platform Foundation known limitations in different locations:

For more information about product known limitations or issues, see Known issues.


If you are developing globalized apps, notice the following restrictions:

The Server Configuration Tool has the following restrictions:

IBM MobileFirst Platform Operational Analytics has the following limitations in terms of globalization:

You might also experience restrictions or anomalies in various aspects of globalization because of limitations in other products, such as browsers, database management systems, or software development kits in use. For example:

Application Center mobile client

The Application Center mobile client follows the cultural conventions of the running device, such as the date formatting. It does not always follow the stricter International Components for Unicode (ICU) rules.

The Application Center mobile client for BlackBerry has the following known limitations:

Application Center mobile client: refresh issues on Android 4.0.x

Android 4.0.x WebView component is known to have several refresh issues. Updating devices to Android 4.1.x should provide a better user experience.

If you build the Application Center client from sources, disabling the hardware acceleration at the application level in the Android manifest should improve the situation for Android 4.0.x. In that case, the application must be built with Android SDK 11 or later.

Rich Page Editor

The Rich Page Editor fails to show the page when the code that initializes it attempts to communicate with MobileFirst Server.

The Rich Page Editor simulates the mobile device environment without any connection to a real server. If the code that initializes the page tries to communicate with MobileFirst Server, a failure occurs. Because of this failure, the page content remains hidden, and we cannot use the Design pane of the Rich Page Editor.

As an example, a failure occurs if the page calls an adapter procedure in the wlCommonInit() function or the wlEnvInit() function.

In general, however, the initialization code is not strictly necessary to get a reasonable visual rendering of the page. To avoid this limitation, temporarily remove the "display: none" style from the body element in the page. Your page then renders even if the initialization functions do not execute completely.

The standard Eclipse editor does not handle UTF-8 with the BOM (byte order mark) properly, therefore the Rich Page Editor does not support UTF-8 with byte order mark.

The Rich Page Editor supports jQuery mobile 1.4.2. It does not support jQuery mobile 1.4.1

JSONStore resources for iPhone and iPad

When you develop apps for iPhone and iPad, the JSONStore resources are always packaged in the application, regardless of whether you enabled JSONStore or not in the application descriptor. The application size is not reduced even if JSONStore is not enabled.

Analytics page of the MobileFirst Operations Console

Response times in the Analytics page of the MobileFirst Operations Console depend on several factors, such as hardware (RAM, CPUs), quantity of accumulated analytics data, and IBM MobileFirst Platform Operational Analytics clustering. Consider testing the load before integrating IBM MobileFirst Platform Operational Analytics into production.

Deployment of an app from MobileFirst Studio to Tomcat

If we use Tomcat as an external server in Eclipse (for example to test and debug the applications directly in MobileFirst Studio), the following restrictions apply:

To avoid these issues, keep the default value of the context path of the project, which is the project name.

IBM MobileFirst Platform Foundation components cannot contain multiple environments

During the creation of a MobileFirst component, you include Android as well as iPhone or iOS environments. The addition of the same component fails because it contains multiple environments.

Separate MobileFirst component needs to be created for each environment, such as Android, iOS or iPhone.

Installation on a cluster of IBM WebSphere Application Servers Liberty profile that you administer with a collective controller

The following limitations apply if you install MobileFirst Server on a cluster of IBM WebSphere Application Servers, Liberty profile, that you administer with a collective controller:

No white space with Eclipse workspace path

The MobileFirst Development Server (an instance of the WebSphere Application Server Liberty profile server) cannot handle an Eclipse workspace path with white space. As a result, a simple app cannot be deployed or previewed. Do not use an Eclipse workspace path with white space.

Installation of a fix pack or interim fix to the Application Center or the MobileFirst Server

When you apply a fix pack or an interim fix to Application Center or MobileFirst Server, manual operations are required, and you might have to shut down your applications for some time. See Upgrading to MPF v6.3.0 or Upgrading to MobileFirst Server v6.3.0 in a production environment.

FIPS 140-2 feature limitations

The following known limitations apply when we use the FIPS 140-2 feature in IBM MobileFirst Platform Foundation:

For more information about this feature, see FIPS 140-2 support.

Support for Android Emulator 2.3.x

MPF does not support Android Emulator 2.3.x because of known issues, as detailed in the Android list of issues at https://code.google.com/tech/android/issues/list (search for issue 12987).

User Certificate Authentication feature limitations

The following known limitations apply when using the User Certificate Authentication feature in IBM MobileFirst Platform Foundation:

LTPA token limitations

An SESN0008E exception occurs when an LTPA token expires before the user session expires.

An LTPA token is associated with the current user session. If the session expires before an LTPA token expires, a new session is created automatically. However, when an LTPA token expires before a user session expires, the following exception occurs:

To resolve this limitation, you must force the user session to expire when the LTPA token expires.

On certain versions of WebSphere Application Server or WebSphere Application Server Liberty, the exception is still logged, but the session is correctly invalidated. See APAR PM85141.

Support of Oracle 12c by MobileFirst Server

The installation tools of the MobileFirst Server (Installation Manager, Server Configuration Tool, and Ant tasks) support installation with Oracle 12c as a database with the same limitations as in Use complex Oracle connection descriptors.

The database and database users must be created before you run the installation tools. The connection information must be entered using a JDBC URL. See Use complex Oracle connection descriptors.

Liberty server limitations

If we use the Liberty studio server on a 32-bit JDK 7, Eclipse might not start, and you might receive the following error: Error occurred during initialization of VM. Could not reserve enough space for object heap. Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.

To fix this issue, use the 64-bit JDK with the 64-bit Eclipse and 64-bit Windows. If we use the 32-bit JDK on a 64-bit machine, you might configure JVM preferences to mx512m and -Xms216m.

Parent topic: Release notes