Question
Session: {0} has timed out when activating mWO app on Android
+21It shows the error as "Something went wrong trying to communicate with IFS Cloud. Session: {0} has timed out" when activating MWO app on Android. What are the causes for this issue? i get this error sometimes ( not all the time ) even when the TAS server also working fine.
+9Most probably this issue can be solved by granting the relevant “IFS Mobile client framework” activities granted to the mobile user(this could occur because of some network issues as well but please check the relevant activities are granted before going into further investigations ) .
Subash Perera
+12Apart from Mobile App activities, we only need permission TOUCHAPPS_RUNTIME to run the mobile app. IFS Mobile client FW permission needed for mobile admin user in back office.
+14Hi Isuru;
As per the error description, this has been raised from the android FW Touch Apps Access layer. Possibly your server is busy or you have a poor network. If that’s not the case the error does mean more generic and you need to see client logs for any detailed error description. Normally we check TAS is working by login to the admin console. But that does not tell the load on the server. The error is nothing to do with user security.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.