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

Chapter 1. Release Announcement

For more information about this release see the Red Hat Developer’s blog post.

1.1. iOS 10, Swift 2.3 and Swift 3.0 Tech Preview

This release of RHMAP includes a tech preview of Swift 2.3 and Swift 3.0 functionality. Using Swift 2.3 or Swift 3.0 allows you to use Xcode 8 and iOS 10 specific features, such as iMessage app extensions. Build Farm support is not part of this preview. If you create a Swift 2.3 or Swift 3.0 app, you must build your app locally. For more information, see Swift 2.3 and Swift 3 Tech Preview

1.2. Android N Tech Preview

This release of RHMAP includes a tech preview of Android N functionality. Build Farm support is not part of this preview. If you create an Android N app, you must build your app locally. For more information, see Android N Tech Preview

1.3. RHMAP Command Line Tool (FHC) Version 2

With this release of RHMAP the default version of the RHMAP command line tool (FHC) changes to Version 2. For an introduction to fhc, see Getting Started With FHC. For more information about FHC Version 2, see the FHC repository.

1.4. Default Node.js Version Changed to Version 4.4

With this release of RHMAP the default version of Node.js used for new apps is Version 4.4. See Section 3.2, “Node.js Versions 0.10.x and 0.8” for information about Node.js deprecation.

Chapter 2. Known Issues

2.1. The App Store logs section under Mobile App Management in the Studio does not display any logs

Navigating to the App Store Apps sidebar menu item under the Mobile App Management header tab displays a list of apps from the private App Store. Clicking on any of the listed apps and navigating to the Audit Logs tab displays a list of logs. Subsequently navigating to the App Store Logs sidebar item results in no logs being displayed even when there are logs available. This prevents you from accessing the audit logs from the sidebar, but you can still access them by navigating to individual app and then clicking the Audit Logs tab.

2.2. Lists on Project and Environment tabs are not sorted based on creation time

The lists for Projects and Environments in the Studio are not sorted based on creation time. There is no workaround available for this issue.

2.3. When deploying a Cloud App using the Studio, the progress bar sometimes hangs on In progress even after the App has been successfully deployed

The progress log bar on deploy screen is still in an In progress rather than Success state. The deployment history table entry for this deploy is marked as Complete/Success, but the progress bar does not reflect this. When this issue occurs, the App is actually deployed and it is safe for you to ignore the progress bar and continue normally.

2.4. Performing certain actions in the Forms management section in the Studio results in errors

Performing certain actions in the Forms Management section of RHMAP Studio results in error messages with status codes 408 and 503. While not explicitly stated in the corresponding error messages, these errors occur because the MBaaS for the current Environment is unreachable via the specified route. To work around this problem, you need to manually update the MBaaS access route for the Environment, or delete the Environment that references the unreachable MBaaS.

2.5. RHMAP 4.x: Pushing from Environment Variables Screen Corrupts Some REDIS Environment Variables

On the Environment Variables screen in the Studio, you can push any environment variables to your OpenShift 3 Cloud App. However, if you do this and Cloud Apps deploy to Openshift 3, the FH_REDIS_HOST and FH_REDIS_PORT environment variables in the Cloud App DeploymentConfig will be removed. If you don’t intend to use the fh.cache API, or you don’t intend to push any custom environment variables from the Studio, this issue does not affect you.

If you encounter this issue, the fh.cache API in the Cloud App will not work.

To workaround this issue:

  1. Make a note of the current values of the 2 environment variables, FH_REDIS_HOST and FH_REDIS_PORT before pushing environment variables to your Cloud App from the Studio. The values can be found in the Environment Variables screen of the Studio.
  2. Push your required environment variables to your OpenShift 3 Cloud App.
  3. Manually set the values for FH_REDIS_HOST and FH_REDIS_PORT in the Cloud App DeploymentConfig using the values noted in step 1.

If you have already pushed environment variables to the Cloud App, and the FH_REDIS_HOST and FH_REDIS_PORT env vars have been removed, it is possible to determine what the values should be:

  • The FH_REDIS_PORT value is always 6379.
  • The FH_REDIS_HOST value starts with redis- and has the same suffix as the Cloud App service. For example, if the Cloud App service is nodejs-1474446716082eh2c, the FH_REDIS_HOST value is redis-1474446716082eh2c

2.6. Cordova Light Push Apps Not Building

Building apps that are based on the Cordova Light Push template will fail. To fix this problem, edit the package.json file and move all entries from devDependencies to dependencies.

2.7. CocoaPods Project Build Errors

If you create an iOS project using CocoaPods it may encounter a race condition during CocoaPods repository initialization, and you may see an error similar to the following:

Build error: 'Updating local specs repositories\n\n[!] CocoaPods was not able to update the `master` repo. If this is an unexpected issue and persists you can inspect it running `pod repo update --verbose`\n'

To workaround this issue, trigger the build again.

2.8. Building UnifiedPush Server (UPS) Android Apps

If your application is based on the Android Push Template, a re-registration to the UnifiedPush Server is not effective and users still receive notifications related to the previous registration. To fix this problem, upgrade the Android SDK dependencies to 3.2.0 and the UnifiedPush SDK dependency to 4.0.2 by editing the app/build.gradle file and adding updated versions for fh-android-sdk and aerogear-android-push. For example:

dependencies {
    compile 'com.feedhenry:fh-android-sdk:3.2.0'
    compile 'com.android.support:appcompat-v7:23.1.1'
    compile 'org.jboss.aerogear:aerogear-android-push:4.0.2'

Chapter 3. Deprecated Features

3.1. Cordova Light

Cordova Light is deprecated and will be removed in a future release of RHMAP.

3.2. Node.js Versions 0.10.x and 0.8

Node.js version 0.10.x and 0.8 are deprecated and will be removed from RHMAP on Jun 30th 2017.

Chapter 4. Resolved Issues

4.1. General Issues

  • RHMAP-11063 - IOS builds timing out due to npm install
  • RHMAP-11011 - Expired profile causes iOS build timeout
  • RHMAP-1902 - 'tag' parameter to fhc build is confusing and broken
  • RHMAP-7727 - Fixes to Welcome App
  • RHMAP-11059 - Get my location is not working in Welcome App (Android)
  • RHMAP-8661 - API Blueprint not showing details of responses
  • RHMAP-9456 - "fhc build" does not populate "credential" field in studio build history
  • RHMAP-9849 - Cannot delete documents that have invalid _id value from Data Browser UI / $fh.db
  • RHMAP-10229 - "All Variants" option when sending push notifications does not work
  • RHMAP-10243 - Forms - Rules do not apply to pre-selected fields
  • RHMAP-10728 - Forms - Rule value field is deleted after result is added
  • RHMAP-10736 - Forms - Lifecycle Deploy - Team with read permission for forms cannot read forms
  • RHMAP-10991 - Forms - Submissions Export is pointing to 'https://files.feedhenry.me'
  • RHMAP-11217 - Forms - Cannot create Forms Project from existing project
  • RHMAP-11349 - Forms - Do not submit value in hidden field
  • RHMAP-1925 - Forms - Clicking on Deploy Form does not take me out of the screen
  • RHMAP-11173 - WFM - Templates are not building
  • RHMAP-11367 - WFM - Move RainCatcher documentation to RainCatcher github organization
  • RHMAP-11411 - WFM - Template - Wrong repo in package.json
  • RHMAP-10263 - Error in snippet code generation (Discover)
  • RHMAP-10286 - $fh.service method parameter is case sensitive
  • RHMAP-10437 - Dropdown does not work properly on the analytics details view
  • RHMAP-10585 - Dead link to dotnet sdk when importing project
  • RHMAP-10705 - MAM - App Store Logs - not showing any logs
  • RHMAP-10852 - Project connections screen causing browser to kill screen when large number of connections
  • RHMAP-10905 - ngui does not add CSRF tokens for some requests
  • RHMAP-10907 - Message improvement when duplicate key for MBaaS target
  • RHMAP-10911 - Make sure platform can build apps via http proxy, and config file in the apps is using the correct http schema
  • RHMAP-10946 - FHC - Fix the description of usage of 'fhc admin mbaas create' command
  • RHMAP-10947 - FHC - Fix requiring of unnecessary parameters for OS3 MBaaS Targets
  • RHMAP-10951 - Issue with viewing edits in studio editor
  • RHMAP-10979 - Error with all docs redirects that are in home page
  • RHMAP-10987 - Login Screen Appears Incorrect on Safari
  • RHMAP-10997 - Error is displayed when accessing the Environment Variables section for an undeployed environment
  • RHMAP-11058 - Unable to build Ionic template app
  • RHMAP-11061 - Success message when adding a new SSH key is showing the bundle key instead the text
  • RHMAP-11075 - Some requests fail after extending CSRF protection
  • RHMAP-11117 - FH-HEALTH-MONITOR service template no longer works
  • RHMAP-10173 - Cloning an existing app unnecessarily asks if we want to clone the repo
  • RHMAP-10448 - Upgrading database fails when multiple simultaneous upgrades occurring
  • RHMAP-10701 - Preview doesn’t load when click on "Create a link to this preview" button
  • RHMAP-10998 - Check permissions when the index file of an app is being served via the preview
  • RHMAP-11019 - Refresh in the deploy page is required to show the combo with nodeJS version options

Legal Notice

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