Error in application when deploying it in workzone

[robmamba25]

I get some dependency errors in my application once it is already deployed in the Workzone or Fiori Launchpad, however I see them correctly mapped in my dependencies in the Manifest, it is worth mentioning that locally it does work for me, only when I deploy it it throws me those dependency errors, do you know what could be happening, in addition to that when I validate the loaded components in the network I see that some point to sapui5.hana.ondemand.com which is incorrect since it should point to the backend? I thank you in advance, I attach the errors and my manifest

[WouterLemaire]

Work Zone will always try to resolve the dependencies when it finds them in the html5 app repository but when the lib or component is not there it will forward to it to the ui5 resources.

In your case, I guess the app is deployed to BTP and the library or component is in your on-premise system. Workzone cannot resolve this because it is in two different systems. 
easy solution would be to deploy your app to the same system as the component.

alternative would be to configure the path in your xs-app.json to map it with your backend. But you will also have to configure the resource roots for this component in the manifest to avoid it goes to the ui5 resources.

[robmamba25]

Yes, the components are in the backend and I need to reference them. I'm trying with resourceRoots in the manifest and that's how I have my xs-app.json. I hope it works. xs-app.json routes": [ { "source": "^/sap/(.*)$", "target": "/sap/$1", "destination": "S4H", "authenticationType": "xsuaa", "csrfProtection": false }, manifest "resourceRoots": { "sap.io.bpm.sworkfloweditor.lib.reuse": "sap/bc/ui5_ui5/sap/nw_aps_bpm_lib/", "sap.se.mi.plm.lib.attachmentservice": "sap/bc/ui5_ui5/sap/plm_ath_cres1/", "s4.cfnd.sit.reuse": "sap/bc/ui5_ui5/sap/sit_eng04_rc/" },

[FabioPagoti]

I faced similar issues when extending some HCM apps and if was way easier to deploy the app in the on premise system instead of BTP. Unfortunately not everything which can be done in ui5.yaml files can be done in xs-app.json (or at least not in the same way). Also, in workzone is pretty simple to create an app pointing to an SAPUi5 app in an on-premise system - you only need the destination + app id. Moreover, when deploying apps to BTP it's always good to add the "sap.platform.cf" : {"ui5VersionNumber": "1.120.x" } in the manifest file. This is the SAPUI5 version used by workzone when opening an app there. If you do not specify it, work zone always use the most recent SAPUI5 version from SAP CDN. This might break the app or at least will make it slower as in this scenario the library won't be cached.

[rfreitas87]

hi @robmamba25   did you manage to solve your issue?

i have similar issue, xs-app file was updated and under HTML5 apps it seems okay. 

But on Worzone Lauchpad we still with problems  pointing to sapui5.hana.ondemand.com