cancel
Showing results for 
Search instead for 
Did you mean: 

Fiori BAS Local test Failed to load sap-ui-core.js 500

glauco
Active Contributor
0 Kudos

Hi experts.

App is an Fiori Elements worklist.

Error after swapping for new CDS View.

I have this error when testing locally with npm start.

I've already ran npm install thinking in the updates, before testing.
We had to create a new CDS View with BOPF action to this app.

New CDS view was activated with sucess.
I've already updated service name in app coding.
OData service is running fine in maint_service.

Error

package.js

index.html

junwu
Active Contributor
0 Kudos

are you sure it was working before?

Accepted Solutions (1)

Accepted Solutions (1)

glauco
Active Contributor
0 Kudos

Hi.

This error was solved.
Solution was updating ui5 tooling for 1.5.1 in package.json and executing npm install.

"@sap/ux-ui5-tooling": "^1.5.1",

Now I have another error, Entityset unknown even I've already changed for the new name.
But as I think it is a new error. This post is answered. ok?
Many thanks everybody.

Answers (2)

Answers (2)

Dhanasupriya
Active Participant
0 Kudos

Hello

Can you try replacing src in index.html bootstrap with this?

	src="https://sapui5.hana.ondemand.com/resources/sap-ui-core.js"
glauco
Active Contributor
0 Kudos

Hi! I've tryied it once. Unfortunately It Didn't work.

glauco
Active Contributor
0 Kudos

Hi Jun.

>> are you sure it was working before?
I can't remember now, because I deployed it a year ago. Probably local tests worked before.
But I can see local tests work for other app.

For this app, I've already changed lines where point to new OData service and entity set.

But I did a try a npm start for another similar app (Elements Worklist) which I didn't change anything yet, and tested the npm start, and the error is the same.


It has the same codifications as one year ago.
I developed all those apps using UI5 version is 1.84.
Customer UI5 version is 1.84.21 as I can see in FLP in about link.

And I found a sap note 2627627_sap_note.pdf talking about similar symptons, which asked to clean some caches in a transaction.


EDIT: Didn't need this sap note 2627627_sap_note.pdf.