I thought I loved Adalo, but things just randomly stop working in my app. Today, two user fields just aren’t updating that are needed to set a user’s time zone (UTC) offset (because of course we have no control over time zone display). They’re automatically set upon visit of Home Screen. Previously it worked fine, but now the fields just don’t update so all times are displayed wrong.
This is in addition to the issue where my create new event form doesn’t populate a database date-time field (unless I create a new action explicitly updating the newly created field to itself). Plus all the other minor things.
I submitted bug reports for three items and haven’t heard back (not even an acknowledgement). None of what I’m doing is terribly complicated but I’m so frustrated right now, I needed to rant. Adalo is very unreliable to me…
But I shouldn’t have to. It was working fine before today and my test app works like this. If I navigate away from home and come back to home, or refresh the screen it doesn’t work either.
I could try that, thanks. But I feel that we have to keep adding workarounds to get things to just work. This page already has many conditionals so I’m wary about adding more things that could slow it down.
So what’s even weirder is that a user that was previously there is updating these fields just fine, but if I create a new user, it’s just not updating at all. I also tried updating field just with a set number (rather than a calculation) and it didn’t work, I also tried creating a new record and it didn’t work.
It’s like my Adalo database is screwed behind the scenes somehow. And Adalo don’t seem inclined to help out…
To the best of my knowledge, all times are going to appear in the user’s current timezone, regardless of your settings. If you find a way to calculate their current timezone vs a different timezone and post the times in the other timezone, then the user will still see the difference. In short, times are always local.
We have an app where we post times available time slots for several different timezones. The app manager posts those times offseting for that difference - they’re on EST, so they post CST an hour after the actual time etc. No way around that.
Depending on your specific use case about what you’re trying to achieve, I’d recommend finding a different way of doing it.
So this is similar to another issue where I create an event with a time-date picker, but the new record just doesn’t populate the time-date field. All the either fields are fine. But the really weird thing is that other calculations that use that field are calculated. But if you look at the record that field is empty… Go figure.
I put in a Adalo support ticket a week ago, but no one responded.
FYI Adalo does not respond outside of working hours. If you submit a ticket late Thursday or Friday, you probably won’t get a response until Monday or Tuesday.
