E
egarcia
Guest
Hello, How are you calling the JSDO Service? Is it being called on success of the Login Service? The Login Service is now asynchronous in Mobile 3.1. If an app was calling the Login Service as the next action in a list of events, instead of chaining the action using the success (error) handler, it would be possible for the JSDO Service code to execute prior to the Login Service completing and loading the catalog. The solution for this issue is to use the success handler for the Login Service to call the next action, being it the JSDO Service or a navigate to page. Example: A mobile app needs to following services to be called: Session Service -- Login Service -- JSDO Service -- getViewAll Service The Mobile app should call each of the service on success of the execution of the previous service. If the mobile app executes it just as the next action in a list of events, then it is possible that the service would be executed prior to the completion of the previous service. Please check the way that the JSDO Service (and other services) are being called on success of the previous service. Thanks.
Continue reading...
Continue reading...