-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Getting Error: No Displays Detected try dropping screen option #171
Comments
Hi @NirmanSonawane have you given it the Mac permission #156 (comment) |
yes |
In my other machine, it is getting captured, |
🤔 Hmmm, I'm really not sure. From a quick browse I can only find this StackExchange question that has some familiarity to this issue and a suggestion that the graphics card needs to be replaced and 'Apple increased the warranty on the graphics card because of a too high number of failures on the specific card' - https://apple.stackexchange.com/questions/12366/graphic-cards-issue |
@NirmanSonawane did you find anything further? |
Nope, I had to remove the main display detection code and directly execute the screencapture process |
Hey, I'm running into the same issue where no physical screen is connected to our Mac mini. We use a HDMI dummy plug to simulate a connected display so the GPU isn't throttled, but Maybe an option could be added to ignore how many screens are available and just try to execute the |
@bencevans I have tested all possible scenarios with and without physical displays enabled, with one and two monitors, via VNC, and via Chrome Remote Desktop. When a monitor is connected, With remote access and physical monitors unplugged, this method returns nothing. This problem became especially critical after office workers switched to remote work. Nevertheless,
|
Describe the bug
In Mac os 10.15.5, when i call screenshot({
format: 'png',
filename: path.join('check.png')
})
I am getting Error: No Displays Detected try dropping screen option
Expected behavior
The screenshot should get captured
Screenshots
system_profiler SPDisplaysDataType; output
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: