Screen capture broken on macOS 13

[s1hofmann]

Version
3.0.0

Short overview
Grabbing screen content seems to be somewhat broken on macOS Ventura.

Issue occurs on

• Virtual machine
• Docker container
• Dev/Host system

Detailed error description
Grabbing screen content on macOS 13 does not throw an error, but instead of showing the full screen content it just shows an empty desktop

Steps to reproduce error
Use screen.capture to snap a screenshot, check its content

[s1hofmann]

In case screen capture throws an error on macOS Ventura it’s caused by #470

A workaround for this would be:

• Use the latest snapshot @nut-tree/nut-js@next
• Don’t apply any scaling on your display, only use the default resolution

[Yunnathai]

is that 3.1.2-next.20230310000145 ?

[s1hofmann]

@jamninetyfive is that 3.1.2-next.20230310000145 ?

Yes

[yusukeiwabuchi]

@s1hofmann
Hi, Simon!

I used @next but the image data is corrupted.
I tested at all resolutions and the results were the same.
(1024x640, 1280x800, 1440x900, 1680x1050)
Is there any workaround?

MacBook Pro 13 inch
OS: Ventura 13.1
CPU: Apple M2

[Yunnathai]

same~

[chan-shiro]

@s1hofmann

Thanks, now fullscreen screen capture works fine, but, output image of captureRegion is still corrupted.

Any suggestion?

MacBook Pro 13 inch
OS: Ventura 13.1
CPU: Apple M2

[s1hofmann]

There's now a workaround implemented that's available for testing in @nut-tree/bolt@next (sponsors only for now)

https://share.cleanshot.com/Df4npQ0c

/cc @chan-shiro @yusukeiwabuchi

[yusukeiwabuchi]

@s1hofmann

Thank you for your response!
However, I still have a problem...

I cannot take pictures of objects (folders, app icons) and Dock that are present on the desktop.

Actual screen

screen.capture

screen.captureRegion

[yusukeiwabuchi]

@s1hofmann

Sorry.
I did not give permission to VSCode for screen recording.

I have confirmed that it works properly. Thank you very much!

[s1hofmann]

@s1hofmann

Sorry. I did not give permission to VSCode for screen recording.

I have confirmed that it works properly. Thank you very much!

I was just about to write this 😃

So can you confirm the fix works as expected?

[yusukeiwabuchi]

I have confirmed that screen.capture and screen.captureRegion work as expected.