3.20.0 Release Notes

Red Hat Mobile Application Platform Hosted 3

For Red Hat Mobile Application Platform Hosted 3

Red Hat Customer Content Services

Abstract

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

Chapter 1. Release Announcement

The following are now fully supported by RHMAP:

  • iOS 11
  • Android O
  • Swift 4

1.1. Repeating Sections in Forms

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

1.2. iOS Support Updates

With the RHMAP 3.20 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 3.20 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. Cordova Light

In October 2016, Red Hat announced that Cordova Light support would end in November 2017. With the RHMAP 3.20 release, Cordova Light is no longer supported.

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. Misleading Error Messages in Specific Scenarios

If your application requires a CORS preflight check and an error occurs, the text associated with that error is not displayed. For example, if you disable a connection tag in RHMAP Studio for an iOS app, and provide Disabled Status Text, that text is never displayed. Instead, the WKWebView library performs a CORS preflight check, encounters an error and displays a generic JSONP error.

2.3. 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.4. Issue When Building iOS Apps

Building iOS Apps using the default Xcode 10 settings fails. To workaround this issue, set the project to use the Legacy Build System as described in the Xcode 10 Release Notes. Red Hat recommends using Xcode 9 where the default target is iOS 11.

2.5. 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.6. 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.

2.7. $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.8. 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.9. 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.10. 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.

2.11. Studio Unresponsive

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

2.12. 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.13. 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.14. 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.15. 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. 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.

2.17. Export Button

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

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

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.

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.

2.21. Sync Framework

The RHMAP data synchronization framework allows you create mobile apps that provide data sync capabilities as described in the Server-side Developer Guide. However, due to limitations imposed by Apple and iOS, your iOS background apps might not synchronize data as expected. Although it might be possible for a developer to workaround the limitations, Red Hat does not support the framework for background apps, as it is beyond the intended scope of the framework.

Chapter 3. $fh.sync Examples for iOS Swift

The Swift sync examples documented in the Client API Guide are specific to Swift 3. If you are using Swift 4, autocorrect the examples using the Fix button in Xcode before compiling your app.

Chapter 4. Deprecated Features

4.1. $fh.auth API

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

4.2. Integrated App Store

RHMAP includes an integrated app store. Support for this feature is deprecated and will be removed at end of January, 2018.

4.3. Windows Support

RHMAP Support for Windows is deprecated and will be removed at end of January, 2018.

Chapter 5. Resolved Issues

5.1. Studio Not Reporting Deployment

The issue around deploying a Cloud App using the Studio, and the progress bar sometimes remaining at In progress even after the App has been successfully deployed has been resolved.

5.2. Docs tab of an MBaaS Service

The issue around the docs tab of an MBaaS Service that affected versions 6.2.0 and 8.1.0 of fh-mbaas-api has been resolved. A minor upgrade of the fh-mbaas-api from 6.2.0 to 6.2.1 was applied.

5.3. Other Resolved Issues

  • RHMAP-18704 fix crashing bug when logging timeout error in fh-dynoman
  • RHMAP-18579 Investigate invalid API Key error
  • RHMAP-18208 "Error importing your data" is faced if start the upgrade database when the data still be importing
  • RHMAP-17530 Unable to define the quantity of the lines to show into the Logs Tab
  • RHMAP-17429 Unable to use a OCSP environment after editing of the OpenShift Token field
  • RHMAP-17048 Wrong values are shown into the Resource Tab for memory usage
  • RHMAP-17006 Wrong URL for the links into the third instruction into the Integrate Feature
  • RHMAP-16821 Unable to create mbaas target if last part of the mbaas url hostname contains >6 characters
  • RHMAP-16377 "Access Control" under "Service Settings" does not realign properly and covers the tick-box
  • RHMAP-14475 AppStore is not respecting special characters
  • RHMAP-14225 Unable to delete Environment Variable
  • RHMAP-12074 In Resources section, improve the message that appears when don’t have any application deployed in a environment
  • RHMAP-963 auth policy list taking too long to return with large numbers of users (e.g. 730)

Legal Notice

Copyright © 2019 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.