Hey @guygreen63,
Thanks for sharing this.
Weâve seen a few mixed reports about Android devices recently, and weâd really like to double-check things on our end as well.
When you have a moment, could you share a bit more detail about what exactly isnât working with the Camera Capture plugin on your Pixel 9 (Android 16) on your side?
For example:
- what action youâre triggering (take photo / take video),
- what happens on screen,
Any short screenshot or screen recording would also help us replicate the behavior more accurately.
Weâre keeping an eye on this and would love to investigate it further from the plugin side.
Thanks a lot for the heads-up! 
Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi everyone, jumping in late here!
Since âSave to Deviceâ is a blocker on iOS 
, has anyone successfully chained this plugin with a Javascript-to-Bubble bridge to trigger a native âShare Sheetâ?
Essentially:
-
Capture photo (Base64)
-
Pass Base64 to a JavaScript element
-
Trigger navigator.share({ files: [...] })
Would this bypass the memory issues Zeroqode mentioned, or does the navigator.share API still crash on large Base64 strings in Bubble? 
Curious if anyone has tried this route! 
Sorry, I was probably in the wrong thread.
This is not while using a plugin.
It is simply the workflow action of Open Camera on Android (Google Pixel phone, Android 16).
Hi @guygreen63 ,
Thanks a lot for the update and for sharing the screenshots
In this case, since the issue is occurring with Bubbleâs native âOpen cameraâ action and not with any of our plugins, weâre unfortunately not able to investigate it further on our side.
Iâd recommend checking (or opening) a thread on the Bubble forum specifically about:
- Bubbleâs built-in camera workflow, or
- Android 16 / Google Pixelârelated camera issues
There are already a few discussions around recent Android changes, so you may find more targeted help there from the Bubble team or other users facing the same behavior.
If you ever run into anything related to one of our Zeroqode plugins, though, feel free to reach out anytime. Weâre always happy to help! 
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @guygreen63,
Just to close the loop here - weâve checked this on our side and can confirm that the issue has been fixed by Bubble - Android Bug Fix Changelog - #18 by nick.carroll
Bubble rolled out an update to React Native 0.81, which addressed the Android bug that was preventing the native âOpen cameraâ action from opening on certain devices and Android versions (including Pixel / Android 16).
After running a new build, the camera now opens and behaves as expected in our tests.
Thanks for reporting this and for everyoneâs patience while it was being investigated
Weâll consider this resolved from our side.
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
This is what I want to do, save the returned URL in the DB. But how do you get the returned URL? The âSave to File Manager Camera Captureâ workflow object doesnât output the URL?
Hi @matt_heffer ,
Thanks for reaching out!
To save the captured image URL to your database, youâll want to use the pluginâs states rather than looking for a direct output from the workflow action.
After the âSave to File Manager Camera Captureâ action runs, you can access the image data through:
- Plugin state: base64 - for the base64-encoded image data
- Plugin state: media URI - for the media URI/URL
You can then save either of these values to your database field depending on which format works best for your use case.
For a practical example of how to set this up, check out how weâve configured it on our demo page here: zeroqode-native-demo-05 | Bubble Editor
This should show you exactly how to capture and store the image data in your workflows.
Let us know if you need any clarification!
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
