Every component I try to access gives me this problem. I’ve restarted, shut down, restarted, and it’s still the same.
Is anyone else having this problem?
Every component I try to access gives me this problem. I’ve restarted, shut down, restarted, and it’s still the same.
Is anyone else having this problem?
@Santiago,
: PinPad & Adv. Device Detector issue - #2 by Dilon
Thank you and have a great day!
Thanks bro! im going to read that post
It’s an app that’s working as a PWA, everything is active, but it’s a problem I’m having.
@Santiago, is the toggle turned ON or OFF?
Sure, friend! The problem is that it’s a list that was working perfectly fine, but every time I touch the list, this happens, and then it happens in other components as well.
I don’t remember what actions the button in that list performed, so it’s a real headache.
@Santiago, Oh so you’re not only seeing this for components built by 3rd party developers which seeing for components like custom lists, buttons, icons, etc..? Is it a legacy app or a responsive app?
Is an app developed in the new version of Adalo. It’s a custom list with a title and a button with visibility… the list is filtered using an input field… It worked perfectly a while ago, but today I wanted to adjust something and encountered this problem.
I tap text outside the list and it’s fine, but when I tap the list itself, this error appears. Then, I tap all the same text outside the list and the error persists…
Do you see it in every app or in a single app?
Is the app built directly as a responsive app or built as a legacy app which converted that to a responsive app recently?
When you see the message, what happens if you click the ‘Layout’ tab in the component and then again click the ‘Setup’ tab?
Have you submitted a support ticket?
I had to delete the list and recreate it all from scratch! That list was causing problems; when I accessed it, it would cause all the components on any page to display the same error. If I left the page and clicked on another component, it worked fine. The problem only occurred when I accessed that list.
I deleted it and had to recreate it after several months!