Troubleshooting¶

UI5 Server¶

Chrome Redirects HTTP URLs to HTTPS (ERR_SSL_PROTOCOL_ERROR)¶

An HTTPS server or proxy that was previously running on a domain (e.g. localhost), might have set an HSTS header, enforcing Chrome to always use HTTPS for this domain. See https://www.chromium.org/hsts. This makes it impossible to connect to an HTTP-only server running on the same domain.

Resolution¶

You need to delete the HSTS mapping in chrome://net-internals/#hsts by entering the domain name (e.g. localhost) and pressing "delete".

Issues Not Listed Here¶

Please follow our Contribution Guidelines on how to report an issue.

UI5 Project¶

Corrupt Framework Dependencies¶

When using the UI5 CLI in versions lower than v2.9.1 or the @ui5/project module in versions lower than v2.2.6 you might experience build- or runtime issues caused by missing or corrupt files in one or more UI5 framework dependencies. Note that this does not affect other project dependencies, such as reuse libraries, which are installed via external package managers like npm or Yarn.

These issues can be the result of an aborted install during a preceding UI5 Tooling execution. Because of a bug that has since been fixed, UI5 Tooling assumes that the preceding install was successful and uses the potentially corrupted dependency.

Resolution¶

Remove the .ui5/framework/ directory from your user's home directory.

rm -rf ~/.ui5/framework/

Any missing framework dependencies will be downloaded again during the next UI5 Tooling invocation.

~/.ui5 Taking too Much Disk Space¶

There are possibly many versions of UI5 framework dependencies installed on your system, taking a large amount of disk space.

Resolution¶

Remove the .ui5/framework/ directory from your user's home directory:

rm -rf ~/.ui5/framework/

Any missing framework dependencies will be downloaded again during the next UI5 Tooling invocation.