Detect UI5 "Default Version" Bootstrap

[boghyon]

One of the common pitfalls I often see is applications relying on the Default Version - bootstrapping the framework without having any UI5 version specified, which should be avoided as documented and explained also in my replies:

• Themecheck - Urgent Production issue - what have you guys done?! openui5#3631
• "SAPUI5 has suddenly internal load resource error despite no changes in the app" - Stack Overflow

Other community members describe their browser reporting a misleading CORS error on 404 responses (simply missing Access-Control-Allow-Origin) whereas the real cause is often that a UI5 module with outdated Last-Modified is attempting to access a module synchronously that is already removed from the CDN.

Detection: wherever a UI5 CDN URL is defined in the project, for example:

• In HTML
• In ui5*.yaml SAP Fiori tools UI5 version config (url: https://<CDN host name> with the version undefined or ""). According to the linked documentation:

  Starting with ux-ui5-tooling version 1.4.7, if the version property is not set in the ui5.yaml, then the minUI5Version from manifest.json will be used for the application preview. If the version property is set, but it is empty, then the latest SAPUI5 version from https://ui5.sap.com will be used [...].

  If the version property is not set and the manifest.json does not contain minUI5Version either: same as empty version (version: "") --> bootstraps with "Default Version".
• ...

Possible solutions in the report:

• Patch-level independent bootstrap aka. Evergreen Version (LTS only)
• Promote "Renovate" docs#108
• Pick one of the maintained SAPUI5/OpenUI5 versions
• If launching the app without any existing local cache (e.g. in an incognito window) doesn't resolve the issue → Create an OpenUI5 issue or SAP ticket to request cache invalidation of the CDN. → After the CDN cache has been invalidated, try again in incognito.

[barnslet]

It should be noted that LTS (long-term support) versions should be selected as specific versions get deprecated too. I had this problem arise after solutioning as mentioned above.

[boghyon]

@barnslet You were not alone :) it's unfortunately a common issue. I just created a new request to address it:

• Detect use of UI5 release that is out of maintenance or scheduled for CDN removal #793

Thanks!

[flovogt]

JIRA: CPOUI5FOUNDATION-1050

[i556484]

Other community members describe their browser reporting a misleading CORS error on 404 responses (simply missing Access-Control-Allow-Origin) whereas the real cause is often that a UI5 module with outdated Last-Modified is attempting to access a module synchronously that is already removed from the CDN.

Internal incident: DINC0594567

---

same as empty version (version: "") --> bootstraps with "Default Version".

Internal incident: DINC0588466