New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen capture dialog on every AltTab launch #3183
Comments
Hi @ProjectTermina, Thank you for reporting this issue. I'm not sure what can be done about this. It's a terrible news. Apple is going to create frustrated users once again.
Could you please clarify exactly which API triggers the prompt? Maybe there is reference material from Apple you could share? We use various APIs to grab screenshots of window, but also window titles, etc. I'm not sure which calls we would need to replace. For instance, using ScreenCaptureKit to list windows and get their titles [has big limitations I reviewed](Apps using ScreenCaptureKit will not receive these additional prompts in macOS 14.4.). Thank you 🙇 |
The WWDC presentation of ScreenCaptureKit specifically called out CGDisplayStream and CGWindowList. Unfortunately there is no official communication from Apple on the upcoming 14.4 release. @lwouis |
The Core Graphics docs, specifically under Quartz Display Services and Quartz Window Services, might be helpful: https://developer.apple.com/documentation/coregraphics/ There is also a possibility that Apple will change their mind about enforcing this in 14.4. A lot of IT people are very unhappy about this. But I wouldn't count on it, of course. |
Thank you for sharing these resources! Let's wait for the beta to end, and let's see if we have to adapt the app or not. Hopefully they backpedal on this idea 🙏 |
Describe the bug
On macOS Sonoma 14.4 Beta, macOS displays a dialog box on every AltTab startup that says "Allow screen capture in AltTab?" Apps using ScreenCaptureKit will not receive these additional prompts in macOS 14.4.
Screenshots / video
video: https://uofi.box.com/s/s9erpblmg2g89jgt5d7k4vtos6emek85
Steps to reproduce the bug
Your environment
The text was updated successfully, but these errors were encountered: