Hi everyone,
I’m currently cleaning up my app and removed a single unused plugin without making any other changes. However, after merging the branch, Bubble is showing 636 non-conflicting changes—mostly properties across various elements being set to “undefined.”
Is it expected for removing just one plugin to trigger this many updates?
I plan to create a save point and test thoroughly before deploying, but the volume of changes across multiple pages makes this a bit overwhelming.
Any insights or similar experiences would be greatly appreciated.
Thanks!
Some of those issues look like could affect the UI as they seem to read CSS settings are affected.
Yeah, that’s exactly why I kept putting this off but I’ve reached a point where I need to test it. I’m still not fully confident, though, given the sheer volume of changes and how much needs to be retested.
This is just because you optimised the app, which removed empty values from your app JSON.
e.g if you had a min height set to 0px, it might’ve set it to null etc
1 Like
That does happen, but they don’t usually read Min height class or single height as those would be specific properties to the plugin removed via optimize app. Those issues could affect the UI significantly.
Usually when it’s just simple properties removed during optimization they won’t show up as issues in issue checker after. I’m under the impression the plugin removed did some custom CSS work on the elements, whose properies as set in reusable element are now empty after removing via optimization the plugin they referenced
It’s unrelated to the plug-in, they removed a plug-in, but also optimised their app and the latter part is causing this behaivoir
Those properties of reusable with now empty values, most likely referenced plugin element values. No bubble properties from styles have those names.
From screenshots the optimization ran was only to delete the plugin as per visual of single checkbox next to the plugin element and not check next to select all, so the unused properties that if checked get removed during optimization and sometimes cause those issues after are not what’s happening. Those issues of unused properties removed during optimization are for ones on elements that were in use, then not, optimized out, but bubble held dynamic expression on the unused property which is where issues come from post optimization.
Just check screenshot shared by OP of the optimize app step and it will be clearer.
I promise you, in either the above screenshot or another time, OP used optimize their app and included the ‘clean unused properties’ issues. That’s what this is.
If they referenced plugin element values, then it wouldn’t have been flagged as an unused plugin…
@boston85719 @georgecollier
I ran a new experiment to better understand the behavior:
Steps performed:
Observations:
-
When merging this branch into another branch, I still get 635 non-conflicting changes
-
Previously, selecting a single unused plugin resulted in 636 changes
This suggests that even when no options are selected, updates are still being generated. On closer inspection, the changes are not limited to styles—they also include workflow updates.
Some of these workflow changes seem related to:
However, there are also updates affecting workflows that appear to have no issues, which is unexpected.
Additionally, when I revisit the Optimize App section, I still see items listed such as:
Additional context:
Yeah, it should all be safe to merge still. Weird that it does the optimisations even when not asked, but is what it is I suppose and you could make a bug report to Contact | Bubble…
