Bugs in Glide Builder (June 2025)

We’ve just disabled an experimental feature–can anyone still reproduce this issue?

4 Likes

It’s been fine for me since this point.

1 Like

On my end, I encountered the bug on my first app after changing its access from private to public. I left it aside for a few hours. When I came back, the bug was still there. So I published my changes, closed Glide, reopened it, and the bug was gone.

Then I had the same bug on my second app. I did the same thing: published the changes, closed and reopened Glide, and the bug disappeared.

Hope this helps :slight_smile:

2 Likes

I will try this because I have a lot of stuff to do and not being able to work in the builder is really frustrating

1 Like

The problem disappeared and the editor finally started working faster, but lately it was impossible to work. Thanks

3 Likes

Can this be delayed by a few days? I have a large app that I was converting and due to this glitch I am behind schedule.

2 Likes

I think it’s finally working again!!! Thank you Glide team :folded_hands::folded_hands::folded_hands:
I will reply to this topic if I come accross any other bugs in the next day or two.

4 Likes

Yes everything seems to be back to normal. I finally finished working on the feedback from a client. Glad it’s fixed!

4 Likes

We’ve identified the core issue and expect to ship a fix tomorrow.

8 Likes

Recurring issues with the missing action on glide AI. 3rd time I have experience this. Hope the incoming patch can fix it!

1 Like

The AI broke down

1 Like

All integrations are gone

1 Like

Can you show us a screenshot of what you mean?

1 Like

I can’t ctrl+v shared ai component from app A to app B. Is it a bug?

1 Like

The other day I was adding a component to this screen, and removing another, and at some point I had to remove and re-add every single component, because entering data in one component was changing the data in a different component (entering a date in “leave” was altering the amount in “paid”, for example). Adding a new “Paid” component stopped that behavior. Yes, the components were pointing to the correct column – none of that had been altered by me. It is currently working correctly, just adding it to this post in case it’s related to all these other issues…

1 Like