Thanks for your comments.
yes, I use virtual proxy - called vpx
when the widget is called (called widget-examples):
(by the way i see in log two calls like this
So it used the virtual proxy in the call
but this call returns 302 redirect to
Any help appreciated... getting desperate here
adding two screenshots, one of the log , and one of how the widget is rendered, it says something about "invalid css" but i'm not sure it is actual error due to the 302 and 401 and also becuase the widget shows correctly on iframe or in dev-hub (single configuration)
Seems like there is a problem with loading json files. These are widget-specific, there are no json files in extensions (well you could add one yourself, but I don't think it's common). Not sure why you would need them in a mashup though, they are mostly for the property panel. How do you load them? app.getObject() ??
You should probably report this to support and se if they have a solution for you.