Before today, everything in our app worked fine, and we haven’t pushed an update for at least a week. Today, though, after clicking a few buttons (to make changes, create a thing, etc.), all the buttons suddenly stop working. After a page refresh it works temporarily, but then it stops again within 5-10 button clicks. This is on our live and dev apps, making the app useless and our users aren’t very happy about it.
I have a strong feeling this is probably due to some update Bubble released to live apps, though I can’t prove that. Nothing else would make sense, though, since this issue didn’t occur before, and we haven’t published any change to our app. Today alone (as of writing this) there were 12 updates released to Bubble without any opportunity to test them on our apps. It’s honestly unacceptable.
I have filed a bug report, but posting here to see if others are seeing similar issues.
I would love to see Bubble implement something similar to how WordPress updates work: When WP releases a platform update, each individual website is able to test the update before applying it to their live website. There are NEVER changes made to live websites with WP, and I’d love to see Bubble change this practice to prevent introducing bugs to live apps without giving us a chance to test before applying those changes to our apps.
It looks like it’s a Bubble bug. Without changing our app at all or updating any of our plugins, I don’t see how else it would work fine all week and suddenly have bugs today. Bubble did release 12 updates today alone, so my guess is that it’s yet another case of Bubble releasing bugs to live apps.
Any chance the error you see is something like e.ownerDocument is null? I have a broken app in the same timeframe as your without any change at all in any part of the app.
In my case it’s about the scrolling to an element action that generates an unhandled error that breaks any subsequest client side action. Maybe this is affecting you too.
Bubble support confirmed it’s the “Scroll To” action. The action isn’t completing, creating a snag that prevents any subsequent workflows. They released a patch today that’s supposed to fix it, but I’ll need to test later to see if it’s working properly now.