We ran into an issue where several plugins in BubbleGo suddenly crash. The strange part is that everything starts working again the moment I modify any dynamic property or even just rename an element inside the editor. This happened across three different plugin demos today.
It looks like something in the latest update might be causing BubbleGo to break until a change is made in the editor. I’m not sure whether this affects production, but the crashes in BubbleGo are happening repeatedly.
the mobile team pushed an update to some native libraries recently to satisfy Google play store requirements and unblock people trying to publish to the store.
My guess would be that changes have broken some plugins?
Exactly this. It was a major update, and it would have been nice to give a heads-up to the developers. A lot of stuff has changed in the latest React version.
Totally understand. I’m sharing these with the team. We missed a step here somewhere
@brad.h the critical update the team pushed to address Google play store requirements changed core library dependencies. That in turn seems to have broken many native mobile plugins.
So the short term fix is to remove those plugins, the longer term fix is asking plugin developers to update
I completely understand that the short-term fix is removing the plugins, but I think there’s an important step that Bubble should take here to support both developers and users.
Since this is a closed beta feature, Bubble has the list of everyone participating in the mobile beta plugin editor. It would be really helpful if Bubble could take responsibility for notifying all plugin developers (via email or official announcement) about this infrastructure update and what specifically changed that’s causing the crashes.
Right now, plugin developers are getting bad reviews and frustrated users through no fault of their own - they had no warning that Bubble was updating to Expo SDK 54 and React Native 0.81. Meanwhile, we as users are stuck with unreliable apps and broken functionality.
I’ve personally reached out to the developers of the plugins I use, but honestly, this communication should come from Bubble. An official email explaining:
What changed in the infrastructure (Expo SDK 54, React Native version, etc.)
What plugin developers need to update to maintain compatibility
A timeline or urgency level
This would help everyone get their plugins updated faster and prevent more apps from breaking. It’s a partnership situation - if Bubble updates the foundation, plugin developers need a heads-up to keep building on it.
On a personal note, I spent an entire week rebuilding interfaces and going through rejected iOS builds trying to figure out where the errors were coming from. I finally discovered the issue wasn’t caused by changes I made - it was changes Bubble made to the infrastructure without any notice. That’s a frustrating experience that could have been avoided with proper communication…
Another thing to add here, is that because of how extremely limited Bubble Mobile is at the moment, it is virtualy impossible to build a usable application without plugins. So just “removing” the plugins isn’t an option. We have core functionality of our application that requires plugins.
This behavior is happening again. App’s crash 100% of the time if I open a sheet with a plugin element.
@nocodeventure I’m using your uploadcare plugin on iOS in bubblego.
@fede.bubble what should I do in this case? Has there been another event not communicated to plugin developers? Should I file a bug report?
Like @aj11 mentioned, this plugin is critical to users. Since it’s impossible to upload multiple images without a plugin I can’t simply delete this plugin and reship to users.
@brad.h the engineering team is currently troubleshooting issues with new builds with mobile. Have you ran into these issues with a new build? Or it started crashing out of nowhere?
@brad.h a new BubbleGo version just went out (version 1.13.0). Mind testing again on that version to see if it addresses the issue?
Outside of that, if a particular plugin is causing an app to crash, your best bet is to reach out directly to the plugin developer. We are in contact with plugin developers as well and can provide assistance when it comes to underlying code updates if needed.
