Oracle® Cloud

Oracle Autonomous Mobile Cloud Enterprise Known Issues

Release 18.2.5

E95341-03

June 2018

Supported Browsers

This table describes the minimum requirements for web browsers that supports.
Web Browser Version

Microsoft Internet Explorer

11

Google Chrome

43

Mozilla Firefox

37, 38

Apple Safari

8.0

General

Clicking Cancel in the Create Instance Dialog Redirects to StackRunner Page

When you create an instance of AMCe from the Dashboard in the My Services Console, it opens the Provision an Autonomous Mobile Cloud Enterprise Instance dialog. If you click Cancel before creating a new stack, you are redirected to the StackRunner page.

This is expected behavior, and you don’t need to make any changes to the StackRunner page. You can return to the My Services Console or navigate to another page.

Region Must be Selected for New Stack

The Region field must be selected in the Cloud Stack Manager during stack provisioning, and can't be left at the default "No Preference" (this option is only available in dev environments).

If the Region field is left at the default “No Preference” stack provisioning will fail with an error like the following: 

The service [stack920152OEHPCS] exists in a different site than other selected services in domain [idcs-13b6c30b935944ffb51926c396a53669]]"

Services Must be Restarted Individually After Stopping Stack

Services must be restarted individually. After stopping the stack, restarting the stack fails.

If the Spark enrich job is stopped when another service is restarted, the enrich job must be restarted individually.

Workaround: Start and stop services individually instead of stopping the whole stack. To restart the Spark enrich job, log into the Analytics Pod Service VM, and execute the following: sudo su oracle cd ~/../../cxpf/Manager/service_scripts/provisioning_check/ python check_provisioning_status_rex.py

Analytics

Can’t Connect to RAC Stack

Analytics doesn’t support Oracle Real Application Clusters (RAC) database association.

Scaling Operations Disabled in PSM Menu

The CxAPOD VM and CxACFG service types are greyed out in the PSM menu. Scaling will be enabled in a future release.

APIs

Collection Access Required for All Resources Used As References

When setting up a resource in the Express API wizard, if you attempt to add a reference to another resource that doesn’t have the Include Resource Collection option enabled, the API can’t be saved. If the resource being used as a reference is set up for collection access, it saves without any issue.

Workaround: Enable Include Resource Collection for all resources used as references.

Oracle-Mobile-Name Header Doesn’t Accept HTML Special Characters

The Oracle-Mobile-Name header can’t contain HTML special characters, including <>!*’();:@&=+$,/?%#[].

During a Storage API call, if there are any HTML special characters in the Oracle-Mobile-Name header, the section of the string after the first special character will be removed. For example, if your Oracle-Mobile-Name is TEST<STORAGE>, the “<” character is interpreted as the start of an HTML section, so it trims off the string <STORAGE> and uses TEST for the header value.

Workaround: If you want to include HTML special characters, encode the header value. There are many HTML encoders available online.

Authentication

Can't Modify or Delete CSF Key Containing Special Characters

When you try to delete a CSF key that contains special characters, a success message appears, but the key is still present in the list with empty content. This empty key can’t be accessed to be modified or deleted.

Workaround: Do not create CSF keys with special characters.

Social Login Requires HTTP Basic Authentication

If you enable social login for your mobile app, you must also enable HTTP basic authentication in the mobile backend's Settings page. Note that if you disable HTTP basic authentication, there is no warning message to alert you that social login won’t work.

Bots

Instant Apps Callback URL Isn't Configured

The Instant Apps callback URL isn’t configured by default.

Workaround: Define the callback URL in global config using the steps below.
  1. Get the connectors URL.

    1. In Bots, edit an existing bot with a Webhook or Facebook channel. (If you don’t have one, create a bot and create a Webhook channel.)

    2. Navigate to the Channels page.

    3. Make a note of the Webhook URL. The connectors URL you need for global config is the first part of the Webhook URL, ending with /connectors/v1 (https://......./connectors/v1).

  2. Add the Instant Apps callback URL to the global config settings.

    1. Do a GET to obtain the current global config. The URL to use is <baseURL>/management-api/v1/settings where <baseURL> is the Bots URL without /botsui at the end.

    2. Do a PUT to update the global config and add the Instant Apps callback URL. In the example below, <connectors URL> is the URL you got in step c above (https://......./connectors/v1).

      Note:

      If the settings and configProperties objects aren’t in the existing global config, you need to create them. 
      {
	"settings": {
		"configProperties": {
			"chatbox.urls.callback": "<connectors URL>/callback?state={stateValue}"
		}
	}
}

Pre-Seeded Sample Bots are Broken

Some of the pre-seeded sample bots included with the AMCe installation are not completely implemented and shouldn’t be used.

Only the following pre-seeded sample bots should be used as examples:

  • CrcPizzaBot

  • PizzaBot

  • PizzaBotWithMemory

  • FinancialQnABot

The rest of the pre-seeded sample bots can be ignored or deleted.

Restarting Intent Server During Training Causes Failure

If you restart the intent server or start a new intent server during training, it invalidates the management API, and training must be manually cancelled and restarted.

Workaround: When an intent server fails and a new intent server is started, make the following updates to the BOTS_TRAINING_MODEL table in OMCE_BOTS DB:

  • Change the TRAINING_STATUS for the model from TRAINING to NO_DATA.

  • Set REQUIRES_TRAINING to 1.

Connectors

Fusion Applications Connector

Fusion Apps Connector: Can't Type Space in Attribute Description

When you enter a description in the property panel for a selected attribute in the Fusion Applications Connector wizard, pressing the keyboard 'Space bar' causes the panel to close.

Workaround: Avoid using spaces in attribute descriptions.

Fusion Apps Connector: Property Panel for Attributes Can't Be Hidden

When you click on an attribute in the Selected Attributes column on the Attributes page of the Fusion Applications Connector wizard, a property panel opens. The only way to close that panel is to click on another attribute in the list to open a different property panel.

Fusion Apps Connector: Test Page Returns 415 When Using POST or PUT

In the Fusion Applications Connector wizard, testing PUT and POST endpoints results in errors.

Workaround: Invoke PUT and POST endpoints directly from custom code.

SOAP Connector

SOAP Connector: RC4 Cipher Suites Not Supported

SOAP connectors use Java 7u85, which doesn’t support RC4 cipher suites.

If you are using a SOAP Connector with a SOAP endpoint that requires a SSL certificate, you may get an exception like the following that indicates an issue with the RC4 cipher: javax.net.ssl.SSLException: Server selected improper ciphersuite SSL_RSA_WITH_RC4_128_MD5

Workaround: Delete the RC4 ciphers from the SSL implementation. For example, if you are using Oracle HTTP Server, remove them from the configuration file.

SOAP Connector: WSDL URL Contains SOA Service ID

After migrating a SOAP Connector, you must remove the SOA service ID from the WSDL URL listed as the service location.

If you don’t update the service location, the response code will be 500. For example, if after migration the service location is listed as “http://den00rme.us.oracle.com/soa-infra/services/default/CustomerScoreService!1.0*soa_b9b086e0-1a5b-4988-b87d-3397ef81d98e/client” you must remove the following section: “!1.0*soa_b9b086e0-1a5b-4988-b87d-3397ef81d98e” to leave the following as the correct service location WSDL URL: “http://den00rme.us.oracle.com/soa-infra/services/default/CustomerScoreService/client”.

MAX (Mobile Application Accelerator)

Don't Delete APIs with MAX Dependencies

If a MAX app on a mobile backend is dependent on an API, deleting the API can corrupt the mobile backend. To avoid errors and unintended data loss, don’t delete an API if a MAX app is dependent on it.

Security Tab Isn’t Displayed for Express APIs

MAX applications don’t support alternative security methods, so the Security tab isn’t displayed by default.

Workaround: If you want to use the Express API with a different security method outside of MAX, complete the Express API, export the RAML, and use it as the input for a custom API.

Notifications

Campaign Notifications Fail for Analytics Apps

Campaign notifications aren’t currently supported for analytics apps.

Campaign notifications for analytics apps fail with a 500 error. There is no known workaround at this time.

Metrics API Returns Error When Scheduled Campaign Expires

After a scheduled campaign is launched, the metrics API returns an error that the scheduled date has expired, instead of showing metrics for the campaign.

Social Users Can't Register for Notifications

The Notifications Device Registry doesn’t show the unique Facebook user ID after a user is registered, so notifications can’t be sent to a single Facebook user.

SDKs

Linking App in Xcode Causes iOS SDK Warning

When linking an iOS app in Xcode, you may get warnings from the SDK's IDM library. These warnings can be ignored.

Here is an example of the warning:

while processing /Users/username/Documents/thirdParty/oamms_sdk_for_ios/libIDMMobileSDK.a(OMOAMOAuthMobileSecurityConfiguration.o): warning: /var/folders/xl/qqnv59k114l8s8lw4cxpgd8w0000gq/C/com.apple.DeveloperTools/7.2.1-7C1002/Xcode/SharedPrecompiledHeaders/IDMMobileSDK-Prefix-dwaqcvuthaofoebsgzuarhtitjzi/IDMMobileSDK-Prefix.pch.pch: No such file or directory

Workaround: No workaround is necessary, as these warnings shouldn't cause any problems in your app.

React Native SDK’s POST requests for BLOB format fail in storage

There is a bug in ReactNative which causes an exception when uploading blob files.

Storage

Can't Create New Version of Collection from More Menu

When you select a collection on the Storage page and click More > New Version or Update Version Number the New Version popup doesn’t open.

Workaround: To create a new version of a collection:

  1. Select the collection on the Storage page.

  2. Click Open to go to the collection.

  3. Click Storage in the breadcrumb to go back to the collection list.

  4. With the collection still selected, click More > New Version or Update Version Number.

  5. The New Version popup opens. Fill out the version information and click Create.

User-Isolated Collections Aren’t Currently Supported

Only shared storage collections are supported. The documentation also includes information about user-isolated collections, but this option isn’t currently available.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Cloud Oracle Autonomous Mobile Cloud Enterprise Known Issues, Release 18.2.5

E95341-03

Copyright © 2018, 2018, Oracle and/or its affiliates. All rights reserved.

Primary Author: Jennifer Shipman

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.