Has anyone run into this? I am using the action “Open Camera” as Step 2, then later getting Result of Step 2.
It works as expected when I actually take a picture. However, if the user cancels the camera without taking a picture, I expect all of these to be empty, but instead they’re not:
Result of Step 2 (Open camera) is empty = no
Result of Step 2 (Open camera) 's file name = 1776277112357x947809568274175900
Result of Step 2 (Open camera) 's URL = 1776277112357x947809568274175900
I have no idea what this 1776277112357x947809568274175900 item is. It doesn’t correspond to any files.
Based on the timestamp portion of the ID (1776277112357) the object was indeed created the moment I triggered the “Open camera” action. So it seems the camera created some kind of mystery object that wasn’t saved?
I’ve run into something similar before. It sounds like Bubble is creating a placeholder file object the moment the camera action is triggered, before the user actually takes a photo. When the user cancels, that placeholder sticks around as the result even though nothing was actually saved.
A workaround I’d try: instead of checking if the result is empty, check if the file URL contains a valid extension (like .jpg or .png). If it doesn’t match, treat it as a cancelled action.
You could also add a condition before any subsequent steps that checks Result of Step 2's URL contains ".jpg" (or whatever formats you expect) and only proceed if that’s true.
Might be worth filing a bug report with Bubble on this one though — the result of a cancelled camera action should logically be empty.
The workaround that I found is whether the base64 is empty.
I will submit a bug report when I get a moment.
