You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to help us sort your issue, we ask that you provide the following information:
Mac model: iMac (Retina 5K, 27-inch, 2017)
macOS version: Catalina 10.15 (19A583)
Description of issue
This only started happening when I switched my saver to Brooklyn. I switched back to Aeriel for the time being and it went away, so Brooklyn seems to be the cause. Even if I set "Turn display off after" in the Energy Saver panel to 1 minute, my screen never turns off when using this saver. If I use any other saver, it behaves as expected.
The text was updated successfully, but these errors were encountered:
My gut feeling is that it may be related to this:
https://developer.apple.com/documentation/avfoundation/avplayer/2990522-preventsdisplaysleepduringvideop
Declaration
var preventsDisplaySleepDuringVideoPlayback: Bool <https://developer.apple.com/documentation/swift/bool> { get set }
Discussion
The default value for this property on iOS is true. The defalut value for this property on macOS is false. Setting this property to false does not force the display to sleep, it just doesn't stop the display from going to sleep. Other apps or frameworks within your app can still prevent the display from going to sleep for other reasons.
The docs say it defaults to false, on macOS, but maybe it is a bug in Catalina that the default isn’t what is documented.
General troubleshooting
Required information
In order to help us sort your issue, we ask that you provide the following information:
Description of issue
This only started happening when I switched my saver to Brooklyn. I switched back to Aeriel for the time being and it went away, so Brooklyn seems to be the cause. Even if I set "Turn display off after" in the Energy Saver panel to 1 minute, my screen never turns off when using this saver. If I use any other saver, it behaves as expected.
The text was updated successfully, but these errors were encountered: