Bubble editor incredibly buggy still

Bugs
21

dynamic mapping is blocking legitimate data from being mapped

this seems to happen if you add new data to a page after the initial page load (ie in my example I changed an existing groups data to the input I wanted, then I tried to map it into the field and it wouldn’t map - to get around it I went to another input and mapped it incorrectly, copied and then pasted it where I wanted it)

22

I’m sure this one catches a lot of newbie bubblers out and adds to bubbles user churn and bug reports unnecessarily…

copy paste data from backend always comes with an extra hidden character that doesn’t exist in the actual data and will break any search unless you delete the invisible character at the end

1 Like
23

and I’m reminded why I don’t even bother submitting bug reports…

the responses are so junior and boilerplate it is a complete waste of time.

bubbles response to my dynamic data not mapping bug

"Hi,
Thanks for reaching out. This is Kara from Bubble Support.
When you add data to the page after the initial page load, it may not be immediately recognized as “loaded” by Bubble’s page loading states. The “Page loaded above fold” and “Page loaded (entire)” states only return true when every element visible on the page has finished loading any data needed to display it.
If an element is invisible on page load, it may not start loading its data until it becomes visible, regardless of its position on the page. This means that dynamically added or revealed elements might not trigger the page’s loaded state until they are visible and their data has finished loading.
I hope this information has been helpful - should you still encounter the issue, it would be helpful if you could share a screen recording of what you see on your end. Feel free to reach out at any time—we’re more than happy to assist :blush:."

  1. this is not what I even submitted the bug about
  2. I already shared the screen recording in the initial bug report lol
  3. obviously they didn’t watch the loom - this is almost always the case because they always ask me to send them a screen recording even though I already sent it when I submitted the bug
2 Likes
24

what’s also annoying so that all the bug reports get marked “resolved” even when the bug isn’t fixed.

the support mark it resolved if the dev team are “working on it” or “know about it”

it would be nicer to have a list “we haven’t forgotten about your bug” with a quarterly update or something so it doesn’t feel like bug reports are completely pointless

25

I had responses from all by bugs today that they have all been escalated to the “specialist team”.

Normally when this happens I never hear anything from the specialist team. I’m going to track to see how many of the bugs they actually respond to. 5 have been escalated so lets see.

26

I started a new bubble app and it came loaded with all these additional colors…

The only way to delete this bloat was to delete them one by one and confirm every deletion. Not a great experience.

and it gets worse…

there’s a whole bunch of styles bloating out my style editor! delete here closes the group and then I have to reopen it… another needless step.

2 Likes
27

This has been what I’ve been saying for years now to bubble. Why they do not care enough to ensure any new user has a good experience in order to improve their retention metrics is beyond me.

I have not submitted a bug report since the chatbot introduced so much more friction to the system, but just prior to that ridiculousness I was complaining about the changes they had made to stop including the report number, and summary of the report itself, and the last time I did submit, they had fixed things and began sending emails properly with the details necessary to understand the thread.

Has that changed again? @fede.bubble did the chatbot cause this change to take place again or was there an intentional removal of those types of pieces of information from emails from support regarding bug reports?

1 Like
28

now converting a float to a reuseable doesn’t hold the original type so you have to set it on the reuseable again

the float is also nested within the reuseable so you’d end up with a float within a float. this was working fine only a few days ago lol…

29

more funkiness…

30

I guess bubble is having another bad day today lol…

I keep getting this error in the client side browser.

Oh no!

We’re having some temporary technical difficulties right now. We’re working on the problem as fast as we can!

In the meantime, try refreshing the page or hitting “back” on your browser just in case things are working again…

We’re really sorry!

If this message does not go away within five minutes, please report the following code to the team: 1750155328426x112124218294580750

1 Like