H
hkuijper
Guest
Olistudent, it indeed was a CORS issue. In the developer console of my browser, in this case Chrome, there was a message which confirmed this. The solution I used to fix this, is to start chrome with the --allow-running-insecure-content argument: chrome.exe --allow-running-insecure-content If I build the app to - for example - an .apk, everything works fine. So it seems that this problem only occurs in the designer. Another suggestion would be downloading this plugin, which adds the allow-control-allow-origin attribute to the request header: https://chrome.google.com/webstore/detail/allow-control-allow-origi/nlfbmbojpeacfghkpbjhddihlkkiljbi/related I also found another thread of someone having a similar issue: https://community.progress.com/community_groups/rollbase/f/25/t/10994.aspx
Continue reading...
Continue reading...