I have just contacted bubble support but wanted to inquire if anyone else is expeirencing the same issues. Some conditionals that were previously functioning have stopped. Surprised to see no one else reporting it as even after I have checked some demo apps that use these features I can see they are also producing the same errors. Would be safe to assume I am not the only one expeirecing this.
Calculate Cords to Address is throwing an error due to it now returning a number rather than an address
The native bubble plugin “Draggable Elements” throws an error when attemping to use the conditional “When drop area is dragged over”. Normally it would return a yes/no but is no longer working.
Yes same here all system generated functions are failing like calculate formula - prepare a text plugin are failing. Whole app is not functional due to this.
Same issue with our app. We were getting ready to send out the press release announcing our launch tomorrow! Five demos scheduled for tomorrow too. What channel does Bubble use to communicate with its users? Not a peep on Twitter.
They won’t report anything on their status page because this isn’t an outage. They simply broke stuff and need to address it ASAP (which they usually do in situations like this one). If folks haven’t filed bug reports, you definitely should. Those reports along with Bubble having been tagged in at least three threads now should certainly get their attention.
Also seeing issues with filter constraints and sort by dynamic field name. Filter constraints not recognising fields and only allowing Advanced constraint to be added. Sort by dynamic field name does not allow selection of field.
Also, I know have an error on calls using API Connector plugin. Is anyone else experiencing this?
First off, my apologies for the errors today. I deployed a significant refactor of our type system today and unfortunately a few bugs slipped through between the cracks. I’ve since reverted it, and am working on fixing those bugs locally. Can you give me any more info about the errors you were seeing with Current Date so that I can make sure everything is shipshape before we deploy again?
Hi @alex.stanescu
Appreciate the feedback. It seems all is back to normal :Whew:
My errors had to do with scheduling a future workflow using the current date.