I’m using the Xano/Adalo integration, and when I create a new app from scratch in Adalo (via the Xano/Adalo integration option) it seems to be stuck on the schema from the first app I created, even though the base URLs and backend workspaces that I’m using for the new app are different to the OG app (and I’ve tried three new base URLs).
I’ve checked for caching settings in Xano, cleared the instance caching just in case, and cleared the browser history and caching. Tried different devices and different user logins. multiple new app creations, refreshed the upload (many times). Every time, it just builds the app with the user Collection schema from the old app. Which means that’s what the magic text is mapped to.
If I call the User endpoint from within the app via a custom action, the right schema returns, and I try to map those properties to use in magic text. But it never updates the database collection and instead remains locked to the old user collection schema .
Xano have said this is a known bug in Adalo, and they need to clear it for me. I’ve flagged it with support. However, so far, there has been no luck in resolving.
Does anyone know if we, as users, can manually clear cached data in our workspace (without deleting my OG app, which is published with users). Has anyone had a similar issue and can share the remedy?
We can see that you have already submitted a ticket. We’ve already replied to your ticket with a Loom video that walks through the explanation. Please take a look and let us know what you find.
We’d also encourage you to keep support-related questions within the ticket; it helps us track everything in one place and provides you with faster, more effective assistance
As an explanation: Adalo pulls data directly from the Get User by ID endpoint in Xano Swagger documentation. If the schema there is incorrect, it will show mismatched data. All there is to be done is updating the schema in Xano for the Get User by ID endpoint so it returns the correct structure.
We have escalated this to the dev team to take a deeper look. I don’t have an ETA on a resolution but we will be sure to update here when we know more. If you haven’t already, please submit a ticket so the team can reach out in the event we need more information. Thanks!
I managed to successfully update the Swagger schema - resulting in the right properties pulling through - by running the endpoint and then ensuring I hit the “Set as Example’ button - I do this each time I make a table update in Xano and it now properly updates the Swagger schema - resulting in the correct properties pulling through when I do a collection edit/refresh in Adalo
We’ve pushed a fix for the issue with Xano Collections not updating, and it has resolved the problem for most Makers.
That said, we did notice that some apps still appeared to have the issue. Investigating those further found that the root cause turned out to be setup-related rather than a continuing platform bug.
In most cases, this happens when the data being returned from Xano is not formatted correctly for Adalo to read. For example, if the response returns an empty array or the User GetOne Endpoint is not returning the expected data.
If you have confirmed your setup and are still seeing problems, please reach out to support with your example and we will troubleshoot further.
Thanks again for your patience while we worked through this one!
I just tested again and it’s all working correctly for me now, which updates in Adalo side properly. Thank you Jessi and the team, appreciate the quick action!
.