An issue exists where Cloud App deployments might fail if deployed to multiple environments that are configured to use different MBaaS targets.

If you encounter this issue:

If your OpenShift cluster is behind an outbound HTTP proxy, mail notifications relating to form submissions fail.

To work around this issue, configure your firewall as follows:

If you click submit on a draft or review form, sometimes a check box selection error is displayed, despite the correct selection of check boxes.

To work around this issue:

$fh.db is a Cloud API that supports CRUDL (create, read, update, delete, list). However there is an issue with the list operation if you are using a 8.x version of fh-mbaas-api earlier than version 8.0.3. Red Hat recommends that you update fh-mbaas-api to 9.0.4 or later. For more information, see Upgrading Node.js for Cloud Apps and MBaaS services using RHMAP Studio.

The Data Browser allows you create filters to query data. However, if you create a filter using the _id column, incorrect results are displayed. There is no workaround for this issue.

If you want to develop apps for iOS with Swift using XCode 8.3 or later, you must upgrade the iOS Swift SDK in order to build those apps using RHMAP. To download the latest SDK, see fh-ios-swift-sdk.

Very large files or repos may cause your browser to become unresponsive when accessing the Studio editor.

The lists for Projects and Environments in the Studio are not sorted based on creation time. There is no workaround for this issue at the moment. Studio allows you to sort items, for example, you can view a list of Projects sorted by last update. However, only the current page is sorted, if you click the next page, the sorting is lost. There is no workaround for this issue at the moment.

RHMAP includes a feature that allows you to create a form that triggers an email after each submission. One of the email options is to include the app name, however the emails sent from RHMAP do not include the app name. There is no known workaround for this issue at this time.

If you perform an action that applies to all environments, but one or more environments is associated with an MBaaS that is currently unavailable, you may see messages that are unhelpful. For example, if you delete a form for a project that is associated with an environment MBaaS that is unstable might result in a 401 error. To work around this problem, ensure all MBaaS instances are available.

The Data Browser Export button is incorrectly presented to user as being disabled. However, clicking the button will export data.

Every Client App template includes a Jenkinsfile in the root directory of the template repo. This file is intended for the self-managed Build Farm and does not provide any functionality for hosted RHMAP.

If you try to export BSON data as described in the Server-side Developer Guide, the export fails. To workaround this issue, export data as JSON or CSV.

If you try to export data from the Data Browser, the export may fail due to a database version issue. To workaround this issue, upgrade the database and try again.

To upgrade the database:

If you try to import data as described in Server Side Developer’s Guide, the import fails. There is no workaround for this issue at the moment.

If you enter a name containing special characters when creating a project, and you later decide to delete that project, you are prompted to enter the HTML entity code instead of the special character. For example, if you create a project named Tom’s App, and you choose to delete it, you are prompted to enter the following:

Tom's App

To delete the project, enter the text, including the HTML entity code, as prompted.

If you are using the Sync Framework, note that there is a known issue with iOS apps that use webkit-sqlite for storage. After the app is running for longer than a few minutes, you might encounter storage failures. Use indexDB for storage instead.