Hey everyone! 
I am trying to Optimize my App and I keep receiving the same error everytime.
I deleted all cookies, changed browsers, restarted the computer… 
This is working for you guys?
According to some guys, this action doesn’t work for large applications where you haven’t done this for a while. For example, I can’t use mine anymore in a specific app. It almost always crashes the page. Sometimes the list of items appears, but if I try to delete 1 item, the page also crashes.
I don’t know if the problem is that the list is large and Bubble displays it all at once. I’ve requested in the past that it be possible to have a return based on user-selectable categories, since you can see that we have these separation categories there like Datatype, Field, Option Set, Option, Styles, Properties, etc. But I was not successful in these requests.
Maybe they can fix this at some point, but I hope it won’t be in a distant future where opening my list of items is impossible, even by category, after having made so many changes to the app.
Other things I’ve noticed that may not work properly in large applications:
Issue Checker: The Issue Checker has more problems than usual. Sometimes it doesn’t find all the issues it should unless you visit the pages or REs. And I believe this gets worse over time to the point where it doesn’t find anything except in the page/RE you’re working on. Sometimes, after a merge, it shows issues that don’t even exist and are fixed by reloading the page.
Serch Tool: The Search Tool doesn’t always find all the references it searches for. And like Issue Checker I believe this gets worse over time.
I’ve had this thing crash on me before. And do believe that it is needing an upgrade to always work regardless of app size, but I think it does struggle with larger apps and older apps.
One thing to do first if you can not have it stop crashing, start deleting some of the ‘heavier items’ that you know need to go, like pages and reusable elements. And then try again. If still crashing, start removing plugins that do not need to be there. And then try again. If still crashing, remove the styles that do not need to be there. And then try again. If still crashing, contact Bubble support about a bug in the optimize application feature.
Thanks @Newed and @boston85719…
I think the problem is exatly this. This is one of my larger apps and I don’t use this option for a long time. The curious thing is that this option is much more necessary for large applications than small ones.
Although I’m always doing this work manually (cleaning pages, REs and unused plugins), it’s always nice to have the this automatic help from Bubble to find more places where we can optimize.
This is a concern of mine too. I’ve noticed that currently, if I delete an RE the issue detector doesn’t report anything. Sometimes I change something in an API call and my App stops working… only when I go to the page that is using this call that the issue detector load the errors count.
These two features are extremely important to help with the long-term development of an App. At some point it becomes genuinely difficult to keep track of everything, especially since we have always been able to count on these resources to help us…
2 Likes
It would be so cool if there was a tool that told you everywhere something was used and how you can safely remove it without creating bugs!
2 Likes
Something tells me that a young agency owner will still invent some tool along these lines. Although I think there are many more things deeply nested in the Bubble structure that might make this more complex, but who knows?!
1 Like
Great!
Do you have plans to cover what type of things?
I mean… Reusable Elements, Datatypes, Fields, Option Sets, Options, Attributes, Custom Events, APIs, BEWFs, Plugins?
For example, the new “trigger” identifier in the new WF version is great, but would be nice to have something that could flag unused Custom Events for example. Right now we need to select each one, wait some time to it be checked and then return the amount of triggers using it.
For plugins we need to check for each element, action, etc… before remove it safely.
All of the above currently work except plugins (in the short/medium term, I will allow plugin authors to have their docs uploaded to Buildprint. That will allow plugin authors to offer users the abiblity to debug in Buildprint rather than contacting them for support)
1 Like
@georgecollier , Buildprint is awsome!
But I miss a tool like the Bubble one, where in one click, it scans my App and tells me everything that I can optimize without the need to ask. item by item, precisely because sometimes we don’t even know what we want to ask. The goal is for the system to help us find out.
It will be greate if, with one click, we have a tool that tells us:
- Custom actions that are not been triggered anywhere
- Backend workflows that are not been used
- Reusable Elements that are not bee used
- Plugins that are not been used
- Styles that are not been used
- Datatype fields that have no data and are not been used anywhere
- API calls that we are not using
This will contribute A LOT to reducing the complexity of each application. In addition to security, because we always end up neglecting parts of the application that we don’t use, precisely because we don’t even remember that we’re not using them…
2 Likes