Skip to main content

xSuite Apps for SAP Fiori Installation Guide

Appendix E. Bug fixes

Component

Topic

Bug

Bug fix

Fiori App/iPhone/iPad

External attachment

An attachment opened externally does not have the Finished button in the toolbar, nor does it have a file name.

Update the Fiori app to the current version (Version 1.9.4 and up).

OCI catalog

"" (blank page)

The OCI catalog is not loaded. Instead, a blank page (iFrame) appears.

In the browser console, a "mixed content" warning is output.

If SAP Fiori runs via HTTPS, call the OCI catalogs via HTTPS.

Cancelling not possible

The OCI catalog is not opened in iFrame but rather in the "Top" window.

Though it is possible to place an order, the user cannot exit the OCI catalog without placing an order because the Cancel button is missing.

Reason: In the OCI catalog, either a frame-breaker is used or the internal links have a target such as "_top."

This error can only be resolved by the operator of the OCI catalog.

Web browser

Console (F12)

Error message:

"Uncaught TypeError: Cannot read property 'getElementsByClassName' of null at f.sap.suite.ui.commons.Timeline._startItemNavigation …"

Update/Patch SAPUI5

See also SAP Knowledge Base Article 2509803: Console Uncaught TypeError with control sap.suite.ui.commons.Timeline.

Error messages:

"GET https://<domain>/<path>/wmdgw/fiori/Component-preload.js 404 (Business Server Page (BSP) Error)"

"YYYY-MM-DD HH:II:SS failed to load Javascript resource: wmdxflowfiori/Component-preload.js"

As the file Component-preload.js is not absolutely required, this error can be ignored.

See also SAP Knowledge Base Article 2407556: Failed to load Javascript resource: Component-preload.js.

Error message:

"GET https://<domain>/<path>/fiori/wmd/i18n/i18n_xx.properties 404 (Business Server Page (BSP) Error)"

or

"GET https://<domain>/<path>/fiori/wmd/userexits/i18n/i18n_xx.properties 404 (Business Server Page (BSP) Error)"

Note: "xx" stands for an abbreviation such as "en" oder "it."

When "xx" is equal to "en" : As the default language tile is English, an error message indicating a missing English language file can be ignored.

When "xx" is not equal to "en": In the xSuite App, a language is being used for which there is no language file. Set up the missing language file. For more information, see the publication xSuite Apps for SAP Fiori Development Guide.

Error message:

"GET https://<domain>/<path>/fiori/wmd/i18n/i18n_xx_YY.properties 404 (Business Server Page (BSP) Error)"

or

"GET https://<domain>/<path>/fiori/wmd/userexits/i18n/i18n_xx_YY.properties 404 (Business Server Page (BSP) Error)"

Note: "xx" stands for an abbreviation and "YY" for a locality. Examples: "en_EN" (British English), "en_US" (American Englisch), "de_DE" (German), or "de_CH" (Swiss German).

If differing texts are not required—as may be the case for British and American English, for instance—you can ignore the error message.

Otherwise, the missing language files must be created. For more information, see the publication xSuite Apps for SAP Fiori Development Guide. Note that the locality is not supported by every web browser.

Error message:

Assertion failed: could not find any translatable text for key Xyz in bundle './app/i18n/i18n.properties'

Note: "Xyz" stands for any i18n text key.

Some i18n text modules are not loaded until app initialization. This can lead to this error message at the beginning of app initialization.

However, since the texts are output in the GUI as soon as they are available, this error message can usually be ignored.

Only if the texts are not displayed in the GUI at the corresponding position, you should check whether these texts are actually missing in the i18n text model.

Error message:

The target you tried to get Xyz does not exist! - EventProvider sap.m.routing.Targets

Note: "Xyz" stands for any routing target.

This error message may occur during app initialization, depending on the SAP UI5 version used.

This error message can be ignored.