CGImageCreate returns null on macOS 15.6.1

[kingzcheung]

I don't know why, on my computer, I got the following result using arboard:

thread 'tokio-runtime-worker' panicked at /Users/xxx/.cargo/registry/src/rsproxy.cn-e3de039b2554c837/arboard-3.6.1/src/platform/osx.rs:88:6:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[complexspaces]

Hey there, thanks for the report,

If possible, could I ask you to look around in/record your system's logs while performing whatever operation that causes CGImageCreate to fail? CoreGraphics.framework often logs warning and debug information via os_log when failures occur. On macOS you would use Console.app for streaming these messages. I would also make sure that Include Debug Messages and Include Info Messages under the Action menubar are enabled too.

I'm hopeful this will give us a real error message to work with to narrow down which input the system is rejecting.

[kingzcheung]

I found my app error in console.app; it looks like there's just an error in my data.

CGImageCreate: invalid image data size: 165 (height) x 836 (bytesPerRow) data provider size 27295

Due to my unfamiliarity with cocoa, there were no error messages at the time, leaving me with no clue to start troubleshooting.

[complexspaces]

Sorry, did you figure out the source of the issue since it was closed? Is there any action I need to take here or was it just malformed input data being passed to set_image?

[kingzcheung]

Sorry, did you figure out the source of the issue since it was closed? Is there any action I need to take here or was it just malformed input data being passed to set_image?

Yes, I found the root cause of the problem, and this is indeed not an issue with arboard, but rather due to the incorrect data format passed to set_image. I think what arboard might need to improve is the error message. Since I'm not using arboard directly, I found the error in this library: (https://github.com/tauri-apps/plugins-workspace/tree/v2/plugins/clipboard-manager), as there were no error messages found on macOS (I didn't know that console.app also logs logs), which left me at a loss. However, I have resolved the issue through console.app.

[complexspaces]

That's fair feedback, thank you. I've gone ahead and merged a PR that removes this panic in favor of an error that can actually be handled.

Unfortunately its not possible to programmatically get the underlying error's description when NULL is returned but I left some debugging tips and references at the internal callsite so that cases like yours in the future have clear guidance available on what to look at next.