Thank you Colin.
Having the same issue with two apps, hope this info helps:
App1. This is the app I first noticed it, so in the previewer domain it all works well and in the custom domain it doesn’t show sometimes the home lists, especially when I update something, whatever on the app. Not also customs lists disappeared but also a horizontal chip list. Another thing worth mentioning is that I have a button that only shows if logged in user doesn’t have items in a collection, and that shows, meaning the page thinks there are no items under that filter. So it makes me think that what is not working is the FILTER feature. Usually within a couple hours the issue gets solved. It seems like it is a matter of things syncing with the custom domain.
App2. Had again the same problem, an app that had been published for months without changing anything, and I changed some things yesterday and the custom lists disappeared. I have a replica backup of this app. So, original app in original domain showed the bug. Backup app in backupp domain didnt show the bug. Backup app in original domain DID show the bug, so it seems that definitely is a problem of connecting to a custom domain.
Can someone confirm if this issue is resolved? I’m still facing this issue and I have to refresh it on mobile devices (iOS & Android both) every time the app is loaded.
Create a blank/splashscreen and make it your home screen (set adalo homescreen to it). Than just add an action on screen load to link to your “real” homescreen. that should do the job.
Hey @brunoribeiro with all due respect, that’s not a solution.
This bug has been around since December of last year and has been reported on multiple times, with tickets submitted along the way and it’s never been fixed.
Hello, everyone,
unfortunately the problem with updating content is still there.
In my case the app is cached on the home page, when I reopen it it shows me nothing. I have to go to another window and then back for the info for today to be loaded…
When I used it in ‘web app’ mode from a smartphone, the problem was not there. When published for testing from TestFlight, the problem occurs.