We can’t see all the details of your bug report. But I can see in the reply that support engeneer tried to reproduce the bug in your app. And he didn’t succeed. So before forwarding the ticket to dev team he gives you some default generic instructions to perform and check if the bug still exists. It can be annoying for reporter (especially if you are experienced dev). But once again, this is a rule of thumb in any Service Desk.
For sure, Bubble has a lot of room for support process improvement. At first they should have some support staff outside of US
The issue with bugs in editor is that it never appears if you have freshly opened browser and new tab with the app, it requires some time for it to appear and that makes it super difficult to report.
Not trying to brag or anything, but in objection to your point I’ll say that support is pretty excellent and easy to reach by a simple email when you’re on the dedicated server plan. You get to go straight to the top levels of their support team when you need help. (But also you can completely avoid update issues like this by dragging your feet a bit on manually updating the Bubble editor)
My experience with support is great, it’s responsive and helpful. (Not a dedicated plan).
Support is definitely is not the problem here. Let’s not shift the focus.
Users that’s not willing to fill bug reports either.
Bubble team should change it’s procedures for development, testing and releases.
It worked for me to use the parameter: &issues_off=true. I would recommend implementing a function in the editor that provides the option to disable the issue checker and, at the same time, does NOT allow updating to live if there are errors.
As anybody experienced any improvements? I’ve been unable to get a checkbox to show it was checked in less than 10-15 seconds. Nothing I do in the editor is responding within 10-15 seconds. Things that I should be able to get accomplished in 2 minutes are taking upwards of 20 minutes.
I know @josh said hoping by EOD tomorrow, which was posted 4 days ago, and curious if others who have been experiencing issues raised in this thread have seen any improvements on thier side over the past 72 hours because I personally have not and I’m missing client projected deadlines and budgets because of the 10-15x increase in time it takes to complete almost any task no matter how simple or complex.
Just got a reply from Bubble support for my report about the multiple editor issues that the support agent interpreted the report as to be focused only on latency issues within the API connector.
I sent a report with a 17 minute video explaining the editor is full of issues and that simple functions like checking a box takes 10-15 seconds to see the check and another 5 seconds for the saving… message to go away so that you can then, 20 seconds after clicking the box, move onto another single action.
Also seeing that the automated reply from Bubble support no longer shows the report details for us to reference.
I know this thread is about the editor freezing and generally being unusually buggy and unusable, but there is a connection between that and Bubble support process, where if the support process was improved, these types of issues may be shorter lived. The original post was made 7 days ago, and there is still no resolution.
There has been times there editor was OK, but then the bubble dev team just pushes the changes to live system. Basically with zero versioning from what I can see at least.
You using editor and icons just start changing for example
So what do we expect?
I mean, how hard would it be to spin up a second version of editor, call it beta and then only publish changes to main one after it been tested and stable for some acceptable time!
I mean they already have a local version running on https://local.bubble.is/home So it wouldn’t be so much work.
At least then you can decide to either use stable version or try new functionality in the beta.
Sometimes clicking on a workflow in the editor doesn’t expand the workflow. A full refresh does not always fix the issue… need to close and reopen the browser.
From workflow editor, selecting “Reveal element” correctly switches over to the design editor tab but the element I expected to be revealed doesn’t appear visually and the tree on the left seems to completely detach from the visual editor… clicking on the tree item does not open the design popup for that element. Another full page refresh is necessary.
I experience these issues multiple times an hour, and its very time consuming trying to make changes.
I can also confirm, the editor is absolutely terrible still without the “issues_off=true” URL as well… Can someone @Roody_BubbleSupport provide an update???
Guys hello, I am now reformed,I have been banned for this issue, my fault, no combative language or spam from now on. It has been one week and editor keep crashing, can’t work very slow and when I use editor ,there I see new visual updates but no progress on important ones.
Hey everyone — just want to chime in with a quick update and thank you all for the ongoing patience.
Our engineering team deployed a few new changes today addressing various aspects of the editor, and they’re continuing to work through additional fixes for the remaining behaviors that have been flagged.
There isn’t a catchall fix for the full range of performance slowdowns, so it’s been really helpful getting confirmation from you all on areas where you’re seeing improvements vs ongoing interruptions. (Please continue submitting bug reports if you haven’t already!)
Thanks, and I’ll continue sharing updates as they become available!
Switching tabs become faster thus editing workflows tab. Even faster than previous editor good job. However two issues remain still . 1)Laggy dynamic variable editing 2)double editor crashes and slow
Hey @Roody_BubbleSupport I dont see any performance improvements at all anywhere… Clicking from “plugins” tab to “workflows” etc. still takes about 5 seconds each time.
API Connector is currently “unusable” still… As in, click on “POST” and “GET” takes 5-10 seconds each time with eventual crash
Was terrible today and the forum was down, everything is on fire and a stable editor seems to not be a concern, i lose count of the amount of times i am forced to refresh
