A report like “everyone gets logged out after three or four days” sounds clear, but it does not tell you what failed. First, find out exactly what the person saw.
First, confirm what actually happened
Ask one affected person to show the exact screen they see. There is a meaningful difference between a sign-in form, a blank profile, a loading failure, and a home screen that has lost its user-specific data.
- They see the login form: check the sign-in setup and how long a login should last.
- They stay signed in but data is missing: check the person's account, access settings, and any outside data source.
- It happens right after a release: compare the installed build, release notes, and any changes to the login or startup flow.
- It only happens in a browser: test cookies, private browsing, extensions, and browser-specific storage before touching the native app.
The four checks worth running
1. Make it happen again on one device
Create a test account. Write down the phone or computer, system version, app version, and last successful login. Check it again after the same amount of time. One repeatable problem is easier to fix than screenshots from several app versions.
2. Review how sign-in works
If the app uses an outside sign-in service or a custom action, the login may expire and fail to renew. Do not store passwords inside the app. Check how long the login should last, how the app renews it, and what users see when renewal fails.
3. Check what happens when the app opens
Many apps route a user based on whether a current-user field exists or whether an API call returns quickly. When that check fails, a user can be sent to the login screen even though their account still exists. Test the flow on a slow connection and with a newly created account.
4. Check whether the problem is Adalo or your app
Test a small, clean Adalo project and a second browser profile. If the problem is only in the production app, compare its custom actions, startup logic, and recent changes. If it appears broadly, capture the time, browser, build, and screenshots before contacting support.
Do not hide the symptom
Automatically looping someone back into the app, caching credentials, or removing a login check can make the problem harder to see and less secure. A better repair is explicit: preserve the intended session, show a useful message when it expires, and make the return path short.
A simple handoff checklist
- The exact account affected and whether it is reproducible.
- Device, browser, app version, and installed build.
- The time of the last successful session and the time it failed.
- Recent changes to login, onboarding, custom actions, or data permissions.
- A screen recording from launch to the point of failure.
When your team needs help
Sign-in bugs are normal app work. The larger warning sign is when no one owns app updates, login problems, or the next support request. Rehost can take care of the build, watch for problems, and make ongoing changes while you keep ownership of your accounts and data. Tell us what the logout looks like, and we will help identify the right first check.
FAQ
Does Adalo log every user out after a fixed number of days?
Do not assume there is one fixed period. The behavior can depend on your app's authentication setup, browser storage, native build, and custom actions. Start by reproducing the exact path in your own app.
Should we ask users to log in again automatically?
Only after you understand why the existing session ends. A clear sign-in prompt is better than a loop that conceals a failed authentication or data request.