4.6.0 Release Notes

Red Hat Mobile Application Platform 4.6

For Red Hat Mobile Application Platform 4.6

Red Hat Customer Content Services


This document provides a high-level description of known issues, fixed issues and new features in RHMAP 4.6.0.

Chapter 1. Release Announcement

The following are now fully supported by RHMAP and the hosted Build Farm:

  • iOS 11
  • Android 8.0
  • Swift 4

1.1. Repeating Sections in Forms

RHMAP 4.6 allows you add repeating sections in Forms. For more information, see the Forms documentation.

1.2. iOS Support Updates

With the RHMAP 4.6 release, iOS 8 is no longer supported.

Apple have removed support for 32-bit apps in iOS 11. If you build Cordova Apps for iOS 11, make sure Build Settings for Architectures in Xcode is set to 64-bit.

1.3. Supported Versions of Swift

With the RHMAP 4.6 release, Swift 2.2 and 2.3 ar no longer supported. Red Hat recommends that you upgrade your application to Swift 3 or 4.

1.4. Supported Version of Ansible

The 4.6 Installer requires Ansible 2.4.

Chapter 2. Deprecation Notice

2.1. Node.js v4 Runtime

RHMAP Support for the Node.js v4 runtime is deprecated. The default Cloud App runtime is Node.js v6.

2.2. $fh.auth API

RHMAP Support for $fh.auth is deprecated and will be removed in a future release.

Chapter 3. Known Issues

3.1. 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:

  1. Open the submission from the Review menu.
  2. Unselect the previously selected check boxes, leaving unselected check boxes unchanged.
  3. Click Submit.

3.2. $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.

3.3. 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.

3.4. 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.

3.5. 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-inappbrowser must be upgraded to 1.6.1 or higher
  • com.ionic.keyboard must be upgraded to 2.2.1 or higher. Also note that this plugin is now named ionic-plugin-keyboard.

3.6. Studio Unresponsive

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

3.7. 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.

3.8. 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.

3.9. 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.

3.10. Error Messages If an MBaaS is Unavailable

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.

3.11. Export Button

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

3.12. 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.

3.13. 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:

  1. 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.
  2. Redeploy the Cloud App by clicking Deploy Cloud App in the Deploy section.

3.14. Data Browser Import

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.

3.15. 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.

3.16. 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.

Chapter 4. Resolved Issues

  • RHMAP-18352 fh-mbaas won’t connect to replica set if mongodb-1 node is not running
  • RHMAP-19582 Investigate git url for mongodb-queue in fh-sync package.json

Legal Notice

Copyright © 2018 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.