Error on Post-Processing (Refine option)

First of all, congratulations on the nice app!

Truncated File Extension during Image Post-Processing in Quick Draft for iOS

Environment and Context

• Application: Quick Draft for iOS.

• Integration Target: Obsidian Vault synchronized via iCloud Drive.

• Observed Error: "Resource not created" (or "O recurso não foi criado") within the Obsidian interface. Issue Summary A critical failure in the file-writing routine of the Quick Draft application occurs when utilizing the "Crop" tool within the "Refine" menu. While standard image captures are correctly persisted with a .jpg extension, images subjected to a "Crop" operation are saved to the file system as raw UUIDs without a file extension. This metadata truncation prevents Obsidian from identifying the resource as a valid media attachment. Steps to Reproduce

1. Initiate an image capture using the Camera or Scanner tool within the Quick Draft interface.

2. Select the Refine option on the capture preview.

3. Execute a Crop operation to adjust the image dimensions.

4. Commit the draft to the Obsidian destination (e.g., obsidian-ios-v2).

5. Observe the resulting link in Obsidian, which appears as ![[UUID]] without an extension. Observed Behavior and Root Cause Analysis

• Extension Truncation: The application's History log confirms that standard saves yield filenames such as B626...8B7A.jpg, whereas saves following a "Crop" action yield truncated filenames like 8FA2...8FA5.

• Obsidian Resource Resolution: In the absence of a file extension, Obsidian treats the transcluded link as a reference to a non-existent Markdown file rather than an image.

• Manual Validation: Manually appending a .jpg extension to the affected file within the iOS "Files" app restores correct rendering in Obsidian, confirming that the "Crop" module fails to re-append the MIME-type extension during the final write operation. Expected vs. Actual Results

• Expected: The application should preserve the .jpg or .png extension during the re-serialization of the image object after an edit.

• Actual: The "Crop" operation triggers a loss of file extension metadata, resulting in broken resource links in the target Obsidian Vault.