style manager text not editable after initial edit
data sources on the page not showing up to be mapped
freezing constantly/randomly even after hard refreshes
copy and paste unresponsive
super laggy
I’ve checked my task manager on windows and my internet
RAM at 40%
CPU at 25%
internet 300mbs up and down latency 4ms
tested in 3 different browsers all with the same issues
honestly bubble get your act together and stop yo-yo-ing the editor. one day it’s working great, the next it’s fallen to bits. even intraday it’s inconsistent.
I’m not even doing heavy things in the editor right now and it is frozen and glitchy. I’m just trying to add an element to a reuseable (which has less than 15 elements itself) - so what gives?
I decided to start a tally of all the bugs I’m finding and have been ignoring assuming bubble would fix them eventually… (I’ll keep this list updated)
added elements not adding into the chosen area (just adds to top)
help menu navigation not clickable after a while (haven’t been able to narrow down what causes this but seems to be after an extended time of the tab being open)
page reloads to blank screen and has to be hard reloaded (happens occasionally)
seriously downgraded page load/editor preview load times
initial load of editor page takes ages for the page to finish caching/loading
reuseable element previews inconsistent/not correct to defaulted states
backend data manager super slow to load - slower than building a page with a repeating group to view the data!
new reuseable/page manager search not working on some page loads, works after page refresh
undo/redo not working consistently
on some page loads nothing shows until I click a tab on the left
input focus not holding after/whilst typing into property inputs
values clearing randomly if clicked in property inputs
newly created pages and reuseable elements not showing in menu until page is refreshed (happens occasionally)
right click window appearing away from mouse on right click - often 100 to 200px away
data mapping dropdown not alphabetical - seems to be ordered by created or last modified?
key smash on reuseable renaming can inadvertantly delete everything on the existing page (I think when I click backspace? seems to not be restricted to the reuseable create pop name input field. possibly the input field is not focused on open? - anyway it’s the keyboard shortcuts from the keystrokes that delete the page data)
right click menu being extremely slow to load
removed field from api workflow still has mapping and shows in search - but cannot be removed since the field doesn’t exist
deleted option sets return and display when used with filter
deleted fields and data still returned to page (and data still charged in WU presumably)
no way to delete data from deleted fields once “cleaned up” - the data still displays and it cannot even be cleared
running bulk operation on backend data very often starts with no data in the list, you have to select something then unselect it to populate the full list to process
backend data manager doesn’t show actual data after a change, you have to change tables to refresh the table (feels like a bug since frontend is real time)
occasionally combining elements into a group jumbles the order of them - often in reverse order. happens inconsistently
Honestly where is the QA team on all of these?
I love bubble - but all these bugs are so frustrating especially since I’ve been putting up with them for so long.
@fede.bubble I’m seeing the same issue - For me it appears the Air Keyboard Shortcuts plugin has been deleted Even though it’s definitely still registered within my app.
Same here. Basically halted all development for me, since top priority is working on a few plugins, and suddenly they’re all nonexistent. The plugins still show up in the list, but there’s no actual content (so the elements show as deleted, and the element in the design tab says the plugin has been deleted)
also reminder that submitting bug reports is a great way to make sure the team knows something is not working as it should. The more reports the faster it gets prioritized
Blue highlight lines doesn’t disappear sometimes after clicking off or pressing esc
Back button in the editor isn’t clickable sometimes at all (greyed out), but the shortcut (ctrl + z) still works
Copy-paste is worst than it was. Sometimes doesn’t copy anything or refuse to paste and when it happens, the right click option focus group refuses to close down - requiring page refresh
Drag-n-drop inside the editor glitches way more than it used to. I stopped using it completely and instead, I move elements in the list side instead of the visual editor
When I click off from an objet, it scrolls up the top and I have to scroll all the way back to the bottom to see what I’ve just done. Super annoying.
That’s it for now, but I’ll bring in the rest if it occurs. Hope these will be repaired soon since I’ve got plenty sites to build. Our app just started to take off…
I’m using Windows 11 and Chrome Version 135.0.7049.96
Honestly, the bug reporting process is painful and is not very rewarding, especially since there seem to be frequent bugs to report.
I have to deal with a bot to get to the point where I can just put my data in. If I’m a paying customer and I’m expected to submit bug reports about things that aren’t working, I should get a simple, frictionless form. This is my biggest pet peeve. The bot is annoying and feels somehow condescending.
I have to provide a video every time, even when it’s something as simple as “this is not doing the thing that it’s supposed to do”. ie: right now, in one of my branches, we can’t click on the notes bubble to add notes. If I submitted that as a bug, I’d have to write all that up (along with all the obvious ways we’ve tried to resolve it), go take a video, and fight through the bot to report it. I just don’t have that time.
My app is walled and has different permissions per role, so it’s a pain to describe all that to someone so they can reproduce it on my environment under the exact same conditions.
After submitting a bug report, there is no follow-up on its resolution. The only way I found out the last bug I reported was resolved was by following the forum thread where everyone else was talking about the issue.
I appreciate the usefulness of the bug reporting process, but it just feels like it should be a little easier given the amount of them there seems to be and the reliance on Bubble to have their users report them in order to identify and solve them.
Don’t use bug report, just send an email directly. Hopefully if enough users do that they will fix the silly mistake and bring the form back. Was such a bad move to remove the form.
Just because AI exists, we do not need to use it everywhere, especially since it slows things down in most cases.
Uhhoh…I accidentally hit return while typing the description of the issue. I guess I should had preemptively expected such an error to occur on my side so to take the time to open a text editor to type my response and then copy/paste it, so as to avoid the now expected back and forth between me and support.
Bot doesn’t ask for step by step instructions, is it live or dev…so just makes the entire process longer and more dragged out as now I need to wait for support to email me those questions, reply with the answers and wait for a response to confirm receipt of information.
They should just give us a button choice to submit via form or use chat bot…I don’t think there is any benefit any party involved here having this go through the chat bot, and reality it is just net-negative for all parties concerned.
Afaik, if you send an email it’s probably going to be even slower because the bot routes it as a bug report.
I complained a lot before about the older version of the chatbot where it takes a whole 5 minutes to submit a bug report.
it’s not as bad now. you can provide a screen recording via their tool, send in your own, or write a detailed description— then you’re done and have to wait
the waiting part is the part that takes forever and it getting escalated to tier 2
In my experience, sending email directly is no faster or slower in terms of response, it just makes the process faster than chatting to a parrot disguised as intelligence, now that the simple form has been removed. I’m sure the extra costs, slower submission, less details in submissions of using a chatbot are outweighed by the large overhead of a static form
Even though it’s definitely still registered within my app.
