Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] FPM Explorer error when opening building blocks #4238

Closed
marianfoo opened this issue Mar 19, 2025 · 2 comments
Closed

[DOCS] FPM Explorer error when opening building blocks #4238

marianfoo opened this issue Mar 19, 2025 · 2 comments

Comments

@marianfoo
Copy link
Contributor

marianfoo commented Mar 19, 2025

Hi OpenUI5 Team,

there is a error when opening the building blocks sample in the FPM Explorer.
Is saw this question on the SCN.

I opened the link and i had the same error:
https://ui5.sap.com/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/chart/chartDefault

Image

Error:

FEMockserver.js:214 [MockServer]    stack: 'TypeError: Failed to fetch\n    at Object.loadFile (https://ui5.sap.com//test-resources/sap/fe/core/fpmExplorer/service-worker.js:128:28)\n    at async CDSMetadataProvider.loadMetadata (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEPluginCDS.js:572:28)\n    at async loadMetadata (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6864:18)\n    at async https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6913:28\n    at async Promise.all (index 0)\n    at async createMockMiddleware (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6955:5)\n    at async FEMockserver.initialize (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6763:9)\n    at async setCurrentMock (https://ui5.sap.com//test-resources/sap/fe/core/fpmExplorer/service-worker.js:75:2)\n    at async https://ui5.sap.com//test-resources/sap/fe/core/fpmExplorer/service-worker.js:101:3' }

FEMockserver.js:6951 Uncaught (in promise) Error: Failed to start {
    "generateMockData": false,
    "urlPath": "/sap/fe/core/mock/chartDefault/",
    "metadataPath": "//test-resources/sap/fe/core/fpmExplorer/topics/buildingBlocks/chart/chartDefault/localService/service.cds",
    "mockdataPath": "//test-resources/sap/fe/core/fpmExplorer/topics/buildingBlocks/chart/chartDefault/localService",
    "_internalName": ""
}
    at https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6951:19
    at async Promise.all (index 0)
    at async createMockMiddleware (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6955:5)
    at async FEMockserver.initialize (https://ui5.sap.com/test-resources/sap/fe/test/mockserver/FEMockserver.js:6763:9)
    at async setCurrentMock (https://ui5.sap.com//test-resources/sap/fe/core/fpmExplorer/service-worker.js:75:2)
    at async https://ui5.sap.com//test-resources/sap/fe/core/fpmExplorer/service-worker.js:101:3
(anonymous) @ FEMockserver.js:6951
await in (anonymous)
createMockMiddleware @ FEMockserver.js:6899
initialize @ FEMockserver.js:6763
await in initialize
FEMockserver @ FEMockserver.js:6756
setCurrentMock @ service-worker.js:70
(anonymous) @ service-worker.js:101

When i opened this link with 1.132.1 it worked:
https://ui5.sap.com/1.132.1/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/rte/rteDefault

It also worked with 1.133.0:
https://ui5.sap.com/1.133.0/test-resources/sap/fe/core/fpmExplorer/index.html#/buildingBlocks/rte/rteDefault

Then i tried again without version and it worked again 🤔
It also worked in incognito mode in chrome.

Strange error, maybe it is something with cache, may have a look if you can improve something.

attached is console.log and network trace

ui5.sap.com-1742372633246.log

ui5.sap.com.har.txt.zip

@nikoletavnv
Copy link
Member

Hello @marianfoo,

I am not able to reproduce this issue. Can you give us more information on the browser you have used to reproduce it. Can you confirm that you still get the same error when initially loading the page?

Kind regards,
Nikoleta

@marianfoo
Copy link
Contributor Author

All good, it was the double slash in the initial link that caused the error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants