I’m running into an issue with the Bubble Mobile Editor and was wondering if anyone else has experienced this.
The Issue
I’m using both Open Camera and Open Camera Library actions.
The workflow successfully opens the camera/gallery, and after selecting or taking a photo, the image is returned correctly. I can confirm this because I’m storing it in a custom state, and it displays perfectly in an Image element.
However, when I try to save that same image to the app’s database (either by creating a new thing or making changes to an existing thing), the image field remains empty. No errors are shown, but the image simply isn’t saved.
What I’ve Verified
Camera opens successfully.
Camera Library opens successfully.
Selected image is returned.
Image displays correctly from the custom state.
Database workflow runs.
Image is not saved to the database.
It almost feels like the returned value can be displayed but isn’t being treated as a file that Bubble can upload and store.
Questions
Has anyone encountered this issue with the new Bubble Mobile Editor?
Is there an additional upload step required before saving the image to the database?
Does anyone know whether this is a current limitation or bug in the Mobile Editor?
Also, if the built-in camera functionality is still unstable, can anyone recommend a reliable image upload plugin element available on the Bubble Mobile Plugin Marketplace that works well with the Mobile Editor?
Hi there, I’m successfully using the native mobile ‘Open Camera’ and also using it to set a custom state before saving to the database. Just to confirm - are you choosing the Custom State’s value as what you’re saving to the database?
Step 1: Open Camera
Step 2: Set Custom State (custom state is type text): Result of Step 1 (Open camera)'s URL
When saving:
Create a new thing: (make sure to have ‘photo-URL’ field of type ‘text’): photo-url = custom state’s photo-url
I haven’t run into this exact issue, but I did have something similar where the image looked fine in a custom state but never actually made it into the database. In my case, the problem was that I was saving the custom state instead of the workflow result returned by the camera action. One other thing I’d check is whether the image field expects a file and whether the workflow is receiving the correct value at the moment the database action runs. If everything looks right, it could also be worth testing the same workflow in BubbleGo or a native build to rule out a Mobile Editor issue. I’m interested to see if others have found a reliable workaround because this seems to be affecting more than one person.
What Bubble data type are you using for that image field? If it’s “image” and not “file”, that’s likely the issue - the mobile editor returns a blob reference, not a standard Bubble file object, so it displays fine in a custom state but the database field expects a different structure.
Honestly the mobile editor’s camera actions have always been finicky with the database. The quick workaround I’ve seen work is to pipe that custom state image through a “Convert image to base64” plugin action first, then store it. Or if you’re okay with a third-party element, the “FilePond uploader” plugin handles mobile camera captures way more reliably than the native actions.
What’s your actual use case here? Single image per thing or multiple? The best fix depends on whether you need cloud storage or just simple Bubble file hosting.
Camera opens successfully.
Image is not saved to the database.
