How to debug an Adalo app
Debug an Adalo app by working backwards from the data: bind a temporary text component to the value you expect, remove every filter until records appear, then add them back one at a time, and check that your actions run in the right order, navigation must always come last.
Debugging in Adalo is mostly narrowing down where the data stops flowing. There is no console, so the discipline is to change one thing at a time and always in the same order.
Start from the data, not the design
Put a temporary text component on the screen bound to the value you expect, before you blame the layout.
- A blank value means the problem is upstream, not the component you suspected.
- This check alone saves you an hour of styling guesses.
- Do it before touching visibility rules or styling.
Check filters one at a time
Remove every filter from the list, then add them back one by one until it breaks.
- Confirm records appear with zero filters first.
- Add filters back one at a time, the one that empties the list is the bug.
- Most often it is a filter comparing mismatched property types.
- Or a filter relying on a record never passed to the screen.
Verify action order
Adalo runs actions top to bottom, so ordering mistakes look like broken actions.
- A "Link to" placed before a "Create" navigates away before the record exists.
- Always put navigation last in the action chain.
Check what the screen was given
Screens only know about records passed to them by the link that opened them.
- A wrong detail-screen record means the link passed the wrong item.
- A missing record usually means a menu link passed nothing at all.
- Follow the link backwards from the broken screen to find it.
Reproduce it on a device
Browser preview hides real device behaviour, so retest anything users report on hardware.
- Keyboards covering inputs only show up on real devices.
- Slow networks and permission prompts behave differently on hardware.
- WebView scrolling issues rarely appear in preview.
Common mistakes and how to diagnose them
The form updates the wrong record.
- Likely cause:
- The form is bound to the collection instead of the current record passed from the previous screen.
- Fix:
- Rebind the form to "Current <Record>" and confirm the link that opens the screen passes it.
A button appears to do nothing.
- Likely cause:
- A condition on the action is false, or an earlier action navigated away.
- Fix:
- Temporarily remove conditions and move navigation to the end of the chain.
Data appears in the editor but not in preview.
- Likely cause:
- A logged-in-user filter with no session, or test data owned by another account.
- Fix:
- Log in as a test user in preview and verify the records belong to them.
Everything works for you, not for users.
- Likely cause:
- Your account has records and roles that a fresh account does not.
- Fix:
- Create a brand-new account and walk the whole flow from signup.
Real example: the list that was empty only for new users
A community app worked perfectly for the founder and showed nothing for everyone else. The Events list was filtered by "Logged-in User's City", and city was only set on accounts created before the signup form changed.
Two-minute diagnosis with the method above: bind a text component to Logged-in User's City, see it blank, and the cause is obvious. Testing with a fresh account is the habit that catches most of these before users do.
When you need an Adalo expert
Plenty of Adalo issues are straightforward to fix yourself with the steps above. It usually pays to bring in an experienced Adalo developer when the problem sits deeper in the build:
- The bug only happens in the published app or on specific devices.
- It involves external collections, custom actions or a WebView, so the failure could be on either side.
- It is intermittent, which usually means timing or caching rather than configuration.
- The app is live and the bug is costing you users right now.
Related guides
Adalo external collection not working: common causes and fixes
Missing properties, wrong item counts, empty lists and pagination problems in Adalo external collections, the symptom, the cause and the fix for each.
Why is my Adalo app slow?
The common causes of a slow Adalo app, heavy lists, relationship filters, oversized images and unnecessary data, and what to change for each.
How to set up a custom action in Adalo
Create an Adalo custom action step by step: method, URL, headers, body with magic text, and how to use the response on the next screen.
Adalo app launch checklist
What to verify before you submit an Adalo app: data, accounts, permissions, empty states, uploads and external collections.
Frequently asked questions
Why does my Adalo form update the wrong record?
The form is bound to a collection rather than the current record passed from the previous screen.
Does Adalo have a console or error log?
Not in the editor. Log on the API side for external requests, and use temporary on-screen text components to inspect values.
Why is my list empty?
A filter is excluding everything. Remove all filters, confirm records appear, then reapply one at a time.
Why does the app behave differently in preview?
Preview runs in a browser with your session. Always retest on a device with a fresh account.
How do I test as a different user?
Create a second account and log in as it in preview, do not rely on your own account for testing.
Webnux Tools is an independent product by Webnux Ltd. It is not affiliated with, endorsed by, or sponsored by Adalo, Inc. Adalo is a trademark of Adalo, Inc.