7 support issues and limitations with the Bubble app

When building a no-code application, it’s imperative to know common issues and understand the limitations of your building platform of choice. That way, your building process is more informed, and you avoid any unnecessary, time-consuming roadblocks along the way.

Here are 7 common support issues and limitations you may experience when building with Bubble.

General Issues

Dropdown Elements

Because Bubble “dropdown” elements use the native HTML “<select>” tag, you generally cannot apply styles (e.g. option alignment, border roundness, etc.) to the expanded list of options. For alternatives, you may want to consider plugins.

Scroll Bars

Scroll bars can look a bit different on different browsers and devices, especially in repeating groups. But this is simply because Bubble relies on the end-user’s OS and browser for how a scrollbar should look.

Older Hardware

If you’re using older hardware, like mid-range laptops from before 2012 or desktops from before 2010, you may experience considerable lag while using the Bubble editor.

Platform or Browser

Browser

It’s important to note that all browsers will have different nuances. Although Bubble tries to make the building experience uniform across all platforms, some elements aren’t supported across every platform or browser. Take note of these as you build your app.

Android (mobile)	Currency format for inputs not supported
Safari (mobile)	Popups don’t show until page reload or tilting deviceInput cursor is offset by few lines while typingPage behind open popup is still scrollable
Safari 13+	Safari 13 prevents any 3rd party cookies from going to iframe requests. Because of this, if your Bubble app is running in an iframe, the bubble client will start workflows as the uid of the user that was attributed to it, but will register as no_user server-side, due to the lack of cookies. The mismatch will prevent any workflow from running successfully. As a workaround, set “Do not set cookies on new visitors by default” in Settings > General > Privacy & Security, so that both server and client know that this is an anonymous user.
Microsoft Edge	Due to browser compatibility issues, dropping files from explorer to browser doesn’t work as expected
Firefox	Firefox has a bug with their localStorage persistence when the browser setting “Delete cookies and site data when Firefox is closed” is enabled. Because of this, some behaviors, especially ones involving cookies and iframes, may not work as expected for end users on Firefox with this setting. The most notable known source of error is with Stripe transactions, which may not redirect back to the app correctly. (This is, unfortunately, a bug at the Firefox level. We are monitoring the situation there in the hopes they will fix this soon.)

Browser Version

Additionally, browser versions play a pivotal role in the overall consistency of your Bubble app. Some Bubble features will break with outdated browser versions. The best way to avoid this is to keep your browser updated to the latest version.

Plugin Compatibility

Sometimes, plugins collide with each other and cause unexpected behavior, especially when they share similar resource names. Although plugin developers are always strongly advised to try their best to not overwrite some common parts of the browser code, this doesn’t always happen. Issues such as these are difficult to predict, but the Bubble team documents any compatibility issues until a system of separating plugin code in runmode is implemented.

Fonts

Custom fonts are sometimes rendered slightly differently across different operating systems and browsers. The difference is usually found in their height differences, which may affect element layouts.

Seeking help

No development process is perfect. When you find yourself stuck in a rut, Bubble.io has tons of resources that can help. Here are some tips on how best to use Bubble’s different assistance channels.

Bubble Forum

The Bubble forum is a great space where users can get insight into their queries. Just like any other internet forum, you’re more likely to get a good response if you state your problem clearly. It’s a good idea to give important details like what you’ve done so others can give more informed pieces of advice.

You can also share your app as an open app so others can see firsthand what’s wrong. If your app is sensitive and private, you can instead share screenshots.

Filing a Bug Report

When filing a bug report, include thorough reproduction steps. This eliminates any unnecessary back and forth between you and the Bubble team.

Email

For more general queries regarding the platform or your account, you can get direct support from the Bubble team by emailing support@bubble.io.

What’s Next?

In the world of application development, things can change and go wrong very quickly. But this shouldn’t be a hindrance to you achieving your development goals.

Ready to launch an app for your business? We’re here to get you started. Call us today!