Chapter 2. Known Issues
2.1. Issue with Cordova Apps
There is an issue with Cordova Apps running on iPad iOS 11 using UIWebView. After selecting an item from a drop-down menu, the menu reappears. To work around this issue, select the item again. This is a known Cordova issue, for further details see: https://issues.apache.org/jira/browse/CB-13287
2.2. Issue when building a Client App for the Android platform when using the ‘cordova-plugin-file-transfer’ plugin
If the ‘cordova-plugin-file-transfer’ plugin is in use and you attempt to build the Client App for the Android platform, the error ‘package org.apache.cordova.file does not exist’ appears in the Studio. A verified solution for this known issue is described in detail here.
2.3. Issue When Building iOS Apps
You might encounter the following error when building an iOS App: "Build error: TypeError: Cannot read property 'documentElement' of undefined". To workaround this issue, try building the App again.
2.4. Importing or Exporting Variants
If you navigate to the Push Page for an App in Studio, there are menu items to Import or Export a variant. Neither of these options work as expected. There is currently no workaround for this issue.
2.5. Issue with Forms Using Check Boxes
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:
- Open the submission from the Review menu.
- Unselect the previously selected check boxes, leaving unselected check boxes unchanged.
- Click Submit.
2.6. $fh.db 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. To work around this issue, upgrade fh-mbaas-api to version 8.0.3 or later.
2.7. Issues When Filtering Data Using the _id column
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.
2.8. Upgrading Swift SDK for XCode
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.
2.9. Cordova Plugins
If you use the Build Farm to build Cordova apps and use the following plugins, then you must update them as follows:
-
cordova-plugin-inappbrowsermust be upgraded to 1.6.1 or higher -
com.ionic.keyboardmust be upgraded to 2.2.1 or higher. Also note that this plugin is now namedionic-plugin-keyboard.
2.10. Studio Unresponsive
Very large files or repos may cause your browser to become unresponsive when accessing the Studio editor.
2.11. Sorting of Items in Studio
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.
2.12. WFM Tech Preview Apps
If you created an app using the WFM template from RHMAP 3.14 or 4.2, you can no longer build that app using the Build Farm. To work around this issue, remove the 'hooks' directory from the app directory.
2.13. Editing Items in WFM Tech Preview Demo Portal
WFM includes a demo portal app that allows you create and edit workflows and workorders. However, if you create a workflow or workorder and immediately edit it after creation, your edits might not be saved. To workaround this issue, always navigate to an old workorder or workflow after creating a new workorder or workflow, before attempting to edit or delete the workflow or workorder you just created.
2.14. Form-based Email Notifications
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.
2.16. Export Button
The Data Browser Export button is incorrectly presented to user as being disabled. However, clicking the button will export data.
2.17. Jenkinsfile in Templates
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.
2.18. Data Browser Export
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:
- In the Data Browser section of the Cloud App page in Studio, click the Upgrade Database button in the top right corner, and confirm by clicking Upgrade Now. Wait until the upgrade process finishes.
- Redeploy the Cloud App by clicking Deploy Cloud App in the Deploy section.
2.19. Deleting Projects
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.
2.20. Sync Framework Storage Issues
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.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.