Session information is improperly handled when some native features are invoked, such as the direct update, which leads to an unusable client application after a direct update is detected.
This issue only occurs when the session cookie is configured to be accessible exclusively from a secured protocol (HTTPS) by the application server.
This problem only affects Google Android clients.
Diagnosing the problem
This issue is due to a problem in Worklight native code in the Google Android environment
Resolving the problem
When supporting clients in an Android environment, you must disable the configuration option for the application server to use secure (HTTPS) session cookies.
|Mobile- Speech and Enterprise Access||IBM Mobile Foundation||Device Runtime||Google Android||5.0, 5.0.0, 188.8.131.52, 184.108.40.206, 220.127.116.11||Consumer, Enterprise|