Since the new update, the services for retrieving records from rollbase doesn't work anymore. I have also followed the steps on: http://documentation.progress.com/output/mobile-app-builder/index.html#page/mab/update-projects-with-the-template.html#wwconnect_header and also upgraded the external resources.
What to do?
1) You don’t see any data in the Emulator? If this is the case can you please check console (or network tab) for any errors
2) Is this specific to particular app?
3) Are you trying with Rollbase Public cloud or Private Cloud 3.0.5?
Since the new update, the services for retrieving records from rollbase doesn't work anymore. I have also followed the steps on: http://documentation.progress.com/output/mobile-app-builder/index.html#page/mab/update-projects-with-the-template.html#wwconnect_header and also upgraded the external resources.
What to do?
Flag this post as spam/abuse.
Hi Anil,
We retrieve some information on the homepage, the services on the other pages is working. Its only the main page, before the upgrade it was working. I get the error message below:
Refused to get unsafe header "X-CLIENT-CONTEXT-ID"
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Im using the private cloud: 3.0.5
Hi Anil,
We retrieve some information on the homepage, the services on the other pages is working. Its only the main page, before the upgrade it was working. I get the error message below:
Refused to get unsafe header "X-CLIENT-CONTEXT-ID"
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
Flag this post as spam/abuse.
Hi Anil,
I have deleted all the services from the homepage (JSDO and the getviewall) and put it back. Now its working. Very weird situation...
Hello,
I just wanted to mention that the message regarding "X-CLIENT-CONTEXT-ID" and failed to load resource with "_oeping" might not be the cause of the issue that you were running to. They might probably still be shown now that the app is working.
If the error was returning error 500 for the access other server resources then they could have been an issue.
I am guessing that somehow there was an issue with the way that services were being invoked and this was fixed when you put the service back.
(For example, it is important to initialize/invoke the JSDO Service before invoking an INVOKE service such as getViewAll.)
Thanks.