Is anyone else experiencing a bug with Bubble’s Multiselect Dropdown where the selected value doesn’t show after the page loads?
The data is still being saved to the database, but when it’s displayed in the element, it appears empty. Also, when you select an option, it throws an error in the console.
I’ve already checked multiple projects, and the issue occurs in all of them.
Yes just noticed the same for me - was working earlier today for certain. Have you submitted a bug report?
I just submitted the ticket and really hope it gets fixed soon. I use this element a lot, so this is a pretty big issue for me.
We’re experiencing the same issue across all apps, which is a huge problem for us, especially when it comes to forms
Facing the same problem. We tried updating Bubble to the newest version to solve it - no luck. This is a big problem, and it affects various functionality across our app.
Note that we haven’t updated our app or any plugin before this started happening.
I submitted a bug report to Bubble about this several hours ago and received word that it is affecting multiple users and has been flagged for the engineering team.
I was somewhat relieved to find out it wasn’t just an isolated issue for my app as it was a complete mystery to me as to why the multi select dropdown element stopped working out of the blue.
No word on a fix at this point however.
This was fixed about three hours ago.
For anyone wondering what happened here, this is the response I received from Bubble support:
After investigating further, our team confirmed that the behavior was caused by a regression introduced as part of an improvement to how the Multidropdown element reads its list values. To resolve this, we reversed the affected code deployment and adjusted the implementation so the improvement could continue working without triggering the bug.
We understand how frustrating it can be when something that was previously working starts behaving unexpectedly, especially when there was nothing you could have done on your end to prevent it.
The issue has now been addressed, and our team has also taken learnings from this incident to help reduce the chances of similar regressions happening in the future.
