Still happening in Beta 3 - I've narrowed it down a bit, it appears that any use of WkWebView in a x64 Intel app no longer functions on M1 / ARM macs: Instead, the WebKit process crashes. A standalone ARM build, or a Universal Intel/Arm build work fine. Apple: this is a very bad regression, any insight? I have updated FB11786440 with an XCode sample project to illustrate the crash.

I am no longer seeing this issue in the first beta of macOS 13 Ventura (22a5266r)

This bug is still present in 12.2 release version (Silicon and Intel).

Submitted as FB9835060

Here's what I see when it's not working, and I can reproduce this issue on 3 different 12.1 systems (M1 and Intel):

If I can come up with a reproducible case, I will submit a FB report. I think I'm now seeing the problem with Apple screensavers as well. If anyone can try this test, I'd appreciate it: Test 1: Open System Prefernces / Desktop & Screen Saver Select the "Message" screensaver Click Screen Saver Options and enter some text to display "foobar" Result: the apple logo and text are displayed. Test 2: Close System Prefernces Open System Prefernces / Desktop & Screen Saver Result: although the Message screensaver is selected, the Preview is now blank If you click Screen Saver Options and then Cancel, the Preview now shows up Repeating the test with the "Hello" screensaver does not show the bug.

Interesting - if seems that if we set a 0.5 second timer to call StartAnimation from within the Initialize method, it works again. This is probably safe as long as your screensaver can gracefully deal with StartAnimation getting called more than once.

I've seen this on macOS and it seems to be caused by some videos being rendered in hardware. A solution is to use javascript to create a canvas, draw the currebt video frame into the canvas, then show the canvas while you take the screenshot. That seems to force the video content to really get included in the webView properly and then it shows up in the screenshot.