All products

Diagnose empty image exports with AI

Trace a zero-byte export through capture, format selection and saving, with checks for browser previews and Electron.

Diagnose empty image exports with AI when a file picker appears to succeed but leaves an unusable file on disk. The export-download-debugging skill asks for evidence from two different stages. First establish whether the application captured a real image payload. Then examine how the browser or desktop shell attempted to save it.

A poster tool might render a correct preview but produce an empty file only inside its desktop wrapper. Compare the same export in the browser and record where the outcome changes. A file appearing at the chosen destination proves that the name was accepted. It does not establish that the image bytes reached it.

What it does

  • Check the payload size before blaming the file picker.
  • Match the extension and declared image type to the selected output.
  • Compare a browser preview with the same export in an Electron shell.
  • Test the fallback save path when the preferred mechanism fails.
  • Check disabled, pending and error states so the interface reports the actual outcome.

Install and use

  1. Use a coding agent with access to the application source and an environment that exhibits the failure. The supplied project checks target OpenDesign.
  2. Reproduce the export with a non-sensitive test image and record the payload and save result separately.
  3. Test the corrected path, check the resulting image and run the relevant project tests before accepting the change.

FAQ

Source

Made by OpenDesign (nexu-io). Original skill: export-download-debugging, published on GitHub under the Apache-2.0 licence.

View on GitHub