My app makes me log back in if I am not using the app regularly, and i mean very regularly. Theres no way i can go to launch with this. Been an adalo customer for 5 years and this has never happened before. Also my app is a little slower than usual when clicking between buttons that change screen inputs and visibilities. The log out thing was present before new years, the app speed deficiency is new.
Typically a user will be logged out for a few different reasons.
A logout action (Anything that can trigger an action example: screen action, button, countdown, etc)
20 days of inactivity
If a user clears their cache and browser history for their device.
If you haven’t already, please submit an Adalo | Support Ticket. This way our team can take a look at your app and include as many details as possible, this will allow our team to provide the best insight.
None of this happened, 20 days of inactivity must have an error making it 20 hours for some people or 1 day. Also, 20 days of inactivity is abnormal already, no?
“Very strange reasons why a user is forced to log out:”
20 days of inactivity
Clearing cache and browser history
Why is it necessary to log out a user after 20 days of inactivity? Isn’t it better to simply handle sessions more effectively, such as refreshing tokens or keeping the user logged in with minimal resource usage?
As for clearing cache – this seems equally strange. Cache is meant to enhance user experience and app speed. If clearing cache forces a logout, this suggests that the system overly relies on client-side storage for session management, which seems inefficient.
Wouldn’t it be much better to implement a method where you could force a user to clean their cache (when necessary) without affecting their session or login status?
From my perspective, these reasons feel more like workarounds for deeper architectural issues rather than user-centric decisions. Could you please clarify why this approach was chosen?
None of the 3 happened to log the users out.
I’m currently on a more urgent and critical support ticket and this moved to 2nd to me but yes!! This is happening a lot, like I say, in both OS android & ios.
And to test it, I used the app the last past week and with no doubt, the app logged me out every single day.
If you guys need more info, I’m happy to help here!
All of this is relatively crazy, can’t you just add a zero to the 20 days? Also I am 100% sure that it’s logging me out after 20 hours, not 20 days
Hi @nvrjulian we’ve deployed a large fix to the connectivity between the builder and servers (makers were seeing a yellow banner that kept appearing at the top of their UI) and have implemented a number of other service enhancements. So could you confirm you are still receiving this issue?
One thing that can trip you up is having multiple tabs open for your app. Co-authoring is not supported in Adalo, and working in one tab and then returning to the app in another tab (or a coworker accessing the app) can create a version issue with the server, and result in log out. Please make sure you’re only accessing the app from one tab. We are taking steps to eliminate this from happening entirely.
No, I think you miss understood this issue.
This problem is happening in native app users, not Adalo makers.
The yellow banner you mention is another issue that I think has been solved for now. (I´m continuing to test this issue).
But here we are mentioning another problem, “final App users” (from the adalo database) are reporting constant log out. They have to log in again every time they open the app.
If you guys need more info, please let me know. Julian