Some of us have already run into the issues listed below and learned how to deal with them. However, many may not have faced them yet or may not know how to handle them when they do.
So hereâs a short list with some quick and alternative solutions until Bubble implements a definitive one.
- Issue Checker showing issues that donât actually exist in the app.
This often happens after:
- Merging a branch
- Syncing a branch with main
- Switching between branches
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
- Issue when trying to merge branches with no apparent specific cause.
Sometimes, even without any apparent issue, when starting a branch merging process you may get the following warning (note: the recent alert has a slightly different look, but the error message has the same context).
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
- Duplicate elements appearing after a merge.
This usually happens right after merging, even if you didnât modify that element.
In some cases:
- Selecting one element selects both.
- In other cases, you can select only one.
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
You can also contact the Bubble Team to remove the copy or try do that by yourself, but be careful here.
Usually, one of the duplicates wonât have any workflows attached. So make sure youâre deleting the copy and not the original one. I once deleted the original element and pushed it live without noticing. 
Whatâs strange is that even reverting the merge and redoing it doesnât always fix the issue.
Apparently this is a known issue for the Bubble team (although difficult to reproduce), so if it happens to you and is more complicated to resolve, contact them.
From my experience:
If a branch starts causing this type of issue, avoid reusing it. Delete it and create a new branch from main (or staging, if you use that flow). It seems like once corrupted, future merges keep reproducing the issue.
- Events, actions or workflow folders stuck in infinite loading (or missing).
This often happens after:
- Creating new events/actions/folders
- Deleting events/actions/folders
- Switching between branches
- Creating new branches
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
- Newly created elements canât be referenced
Sometimes, a newly created element doesnât appear in the dropdown list when trying to reference it. Obviously, elements created within RGs canât be natively referenced from outside, which is not the case here.
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
- Editor is so slow that itâs almost impossible to use it.
This one happens frequently, especially in large and complex apps. But there are likely multiple factors involved here such as local system configuration (CPU, RAM, browser, extensions, etc.), network connection, etc. However, some users have also reported what appears to be a memory leak behavior in the editor, which may indicate deeper underlying causes at even more complex levels.
Try this Quick Fix: Refresh the tab. If it persists, close and reopen the editor.
You can (and should) also make use of Reusable Elements, not only to reduce the number of workflows on a page/section, but also to improve the maintainability of the application, condition and isolate logic, and also to remove a very large number of elements in the same section.
- Loss of drag control in the App Search Tool.
If for some reason you move the App Search Tool window to the top and lose control over the drag capability. This also happens sometimes for no apparent logical reason, you just open the window and itâs already âbuggedâ.
Try this Quick Fix: Since refreshing the tab wonât work in this case, you can duplicate the tab, and that will fix the issue.
But if you donât want to refresh the tab or duplicate the tab (which will also reload the page), so you donât lose the current view of what youâre working on, you can use the browserâs inspector, find the child container element of âsearch-pallete-wrapperâ and set a top margin of something like 100px. This will allow you to access the header area, which will allow you to move it again.
- Unable to access the App Data section view.
Sometimes you are trying to access the App Data section, but the app keeps preventing you from doing so, reloading and insisting on displaying another table.
Try this Quick Fix: Duplicate the tab or remove all parameters from the URL after âtype_idâ.
Well, a quick fix to almost of the issues above is to refresh the browser tab, duplicate it or close and open a new one (although it doesnât always work), as it may just be a temporary caching issue.
I even recommend that you make it a habit to always refresh the tab before and after a merge, or even when switching between branches. This will prevent many headaches.
And if youâre like me and have several tabs open all the time (not just Bubble, but various things), it would be wise to close the browser and restore them all from time to time.
Some users have also used other browsers and reported improvements. Well, I have several browsers installed for testing responsiveness and apps/plugins behavior, but Iâve always liked using Chrome as my main browser. You can test others if you like.
Please note that there are several other issues related to specific features, such as the beta version of the Properties Editor, and others.
Iâm not addressing those here. This post focuses only on issues that may arise during general use of the editor and when working with branches. So there are certainly other issues that I havenât listed here because I donât remember them at the moment or because I havenât faced them yet. Some issues may occur in very specific circumstances, so if youâve run into other editor or branching issues and discovered simple (even temporary) fixes that work, feel free to share them with the community. 