zlacker

>>speckx+(OP)
Another trick is to open Activity Monitor, switch to the Energy tab, and sort by the "Preventing sleep" column. Some apps prevent macOS from sleeping.

In my case, I've discovered that Devonthink (document/notes management app) is responsible. I've been meaning to file a bug report about it.

I'm surprised that Apple's power management doesn't have an alert for this. Surely an app that causes my Mac to become glowing hot while sitting in my backpack, not to mention slowly running out of battery, is a pretty important thing to intercept. Meanwhile, I keep being asked if Chrome should be allowed to find devices on my network, which doesn't seem nearly as important.

>>atombe+xg
I didn't realize any rando app could prevent the entire system from sleeping. Shouldn't this power be gated behind a user-controllable permission? I assume the developer needs to at least use an entitlement to call whatever API does this...?

>>ryandr+1i
Any website and app can do it. Zoom / Google Meet / YouTube / Bandcamp / Spotify already does this. I don't think it needs to be hidden behind walls. Maybe a user override can be added.

In Linux, KDE's power manager PowerDevil shows if something is blocking device or display sleep for example. I don't think it's hard to add an indicator in macOS, too.

>>bayind+Vl
Visibility isn't the problem. As OP mentioned, you can go into Activity Monitor to easily see what application is doing this. The user just doesn't seem to have any control over it or any way to stop a particular application from doing it.

>>ryandr+2n
It's buried too deep. Clicking on battery and seeing a line saying "There are apps preventing sleep >" and hovering on it to see a list is way better than digging activity monitor.

Another option might be another section for apps preventing sleep, like power hungry applications.

>>bayind+Jn
Or, when apps try to intercept sleep the OS can pop an Allow/Don't allow dialog before the app can actually achieve this

>>foobar+5s
That'd create a lot of interruptions for the user. Some apps use it temporarily in critical sections, web media players enable/disable when play/pause events happen, etc.

An indicator and selective overrides is the way, IMHO. Invisible if you don't look, but it's there when you need it.