An import worker can see a path before its producer has finished writing the file. In a product-photo workflow, that can look like a broken thumbnail or a failed upload—even when the capture itself was fine.
I work on CartVisual's product-creative guides. This tutorial separates three things that often get bundled together: a camera event, a completed host transfer, and an image that is actually usable.
A camera event is the beginning of a handoff
In the official libgphoto2 tethering example , the GP_EVENT_FILE_ADDED branch obtains the camera file path and then calls gp_camera_file_get to download it. That sequence is a useful boundary: receiving an event does not, by itself, prove that your downstream host-side processing has finished.
Do not copy the example's camera-file deletion into a production workflow without a separate retention decision.…