Hi Team,
Every time we push new app settings to the production, The users are logged out on reloading. Is there a way we can prevent the app from logging out the users when new settings are pushed to the production app?
Hi @Edwin
When new settings are pushed, users get a popup that instructs them to reload the app, reloading should be seamless and they should not get logged out.
Can you explain more about your setup?
Hi @diana
Thank you for the reply. When our users get the reload notification and they click on it, the application reloads and takes them back to the log in page. This has been happening after we upgraded to v 4.10.0
Hi @Edwin
This is concerning, and should not happen. We have a battery of e2e tests that go over the settings upgrade workflow for offline users, and our tests have never shown logouts when settings are updated.
What version were you on previously?
Is this happening for all users or just some?
Hi @diana
Thankyou for your continuous help.
We moved from v3.17.0. To v4.10.0
And the logging out happens for most users not all.
Since this is not a behavior that we’ve seen, can you try to give us more details about the users who are seeing this?
Are they all offline users? Does it happen consistently?
On the about page there is a reload button for the app. Do they get logged out when they click that as well? Are these users logging in through the Android app or on a browser?
hi @diana
Both offline and online users.
It does not happen consistently . Just once . Some vhts it does not happen.
They only get logged out when they press the reload .
The users are logging in through the mobile app.
It does not happen consistently . Just once . Some vhts it does not happen.
Can you please expand on what you mean by “just once”?
Have you tried capturing logs or videos of this?
How are you pushing settings to the app?
hi @diana
The logout does not always happen. That is what i meant by once.
We have not captured the logs or video because the complaints come from the field after they have already been logged out.
I noticed a notification that appeared on my side and then logged me out .
Would this be the reason that they are getting logged out?
The notification is a manifestation of them being logged out. This is not happening because of settings changes. This happens because the user’s session has expired. There can be a variety of reasons for this.
Are the users able to log in immediately afterwards using the same password?
Hi @diana
Thank you for the feedback. No the users are an able to login immediately . They have to contact their supervisors for the credentials. Some times they even travel long distances to get those credentials.
How can we solve this problem so that sessions stop expiring .
Hi @Edwin
Can you check API logs and find which requests are returning 401s for your logged out users?
Have you changed any CouchDb configuration? The default session timeout for CHT CouchDb is one year.