Missing resources folder, when deploying SAPUI5 App to Neo Environment

[former_member626553]

Hi Experts,

I am trying to deploy my SAPUI5 Application to my Neo Environment. In the Application I use an OData Service and the UserAPI.

When I deploy using "/resources/sap-ui-core.js" as a source for the script in index.html, i get a 404 Error (it cannot find the file), however when I run the Application from the WebIDE, it works perfectly fine.

When I deploy using "https://sapui5.hana.ondemand.com/resources/sap-ui-core.js" as a source for the scipt in index.html, it fails to load the OData Destination and the UserAPI (the rest of the app works) and I get following errors:

I am assuming that it does not find my neo-app.js file, where I reference the UserAPI and the Destination.

Is this a bug, or is there an other way to deploy my app without any problems?

Thanks in advance

Noa Junod

[ibibhu · Accepted solution]

Dear noajunod,

Please keep the /resources/sap-ui-core.js as it is , as you said issue is with the neo-app.json file

neo-app.json file was not being included in the “dist” folder when the Web IDE builds the app as a reason after deploying you will get "No destination required" in Required Destinations under

https://<region>.ondemand.com/cockpit/#/acc/<subaccount>/html5app/<you app>/dashboard

Thanks you lucasvaccaro for helping in identifying the root cause.

So few things to note here in ui5.yaml
- app-name
- namespace
You can find your namespace under manifest.json

Please maintain the same in ui5.yaml i.e com/tes/nameSpace
as "sap.app.id" is the combination of <namespace.projectname>

if in your case namespace is empty ie. "id":TacticTool
Please keep the ui5.yaml>namespace empty**

Build and deploy the project.

**Note the above empty namespace is not recommended as Namespace is a mandatory field if you are creating a ui5 application from template now a days

Follow this to know this in more details Reference:ui5uild

Hope so this help.

Regards,
Bibhu

[devendervb]

As you guessed, if we make few changes in neo-app.json, will fix this issue.

To give you a pointer, try to changes resources folder path in neo-app.json , try as /webapp/resources ... like that

Best of luck