Hi @LDC . There is no separate setting on the Go app for this, it is entirely dependent on the Salesforce settings for the session and and refresh token policy. When the Go app forces the user to re-login, it is only because it is responding to the message received from Salesforce on the status of the user's login session. I do see that there is a case open for this issue (00086915), so I will add a comment there on something that can be checked. I want to avoid trying to do separate troubleshooting here while a support case is open, since it could cause confusion.
Exactly the same issue, on FSA the period of inactivity wasn’t enforced but is on GO. Not sure why the difference?
Hi Mark. I'm not sure why there would be a difference either. Like I stated in my comment above yours, when the Go app forces the user to re-login, it is only because it is responding to the message received from Salesforce on the status of the user's login session.
When you are able, I would suggest opening a Case for the issue. If you do, please include as much detail as possible. Some info that could be helpful:
* How often does the issue occur?
* Does it seem to be an issue for all technicians or a smaller subset?
* Does it seem to only happen to technicians in a particular region?
* Does it seem to be device specific?
* Is there a discernible pattern for how long the period of inactivity was before the user's authentication expires?
* Important: after this occurs, if an app log can be obtained from the More -> General -> Send App Logs feature of the app, it could be very helpful if you could attach the log to the case.
Basically, the more info the better as such issues can be very difficult to isolate and diagnose. Anything you may have noticed could be helpful. We aren't having widespread reports of this issue, and we aren't noticing it during internal testing, but we have had a couple reports of this issue for which engineering has not been able to identify why there would be a difference between FSA and Go.
One more additional piece of information to mention. For the 1.7 release (scheduled for mid-December), we are intending to make the "Remember Me" checkbox on the Sign-in screen work properly, so that it is less frustrating for a user to quickly get back into the app when their authentication does expire. Once that feature is working, if it is coupled with the Salesforce Lightning Login, logging back in is much less of a hassle.
See these links for some info on lightning login:
Video of how it works: https://www.salesforce.com/video/1765359/