-
-
Notifications
You must be signed in to change notification settings - Fork 355
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
App doesn’t work without Screen Recording permission granted #3819
Comments
Hello, I have the exact same issue on my MBP M3 Pro with Sequoia 15.0.1 and latest AltTab 7.2.0. If the app doesn't have the Screen Recording permission enabled (disabled in MacOSX setting and the checkbox "Use the app without this permission" enabled) , none of the three available apparence work. Option + Tab does nothing at all. I already tried resetting and reinstalling, no change. Thanks. |
Hi, Could you please both share videos of the issue in motion? Showing the system permissions, AltTab permission window, and the behavior you see when pressing the shortcut? Could you please also click the menubar icon for AltTab and select "Show"? Thank you |
Attaching screenshots instead. Accessibility permissions: ![]() Screen Recording permissions: ![]() AltTab permissions: ![]() AltTab Controls settings: ![]() ![]() AltTab Appearance settings: ![]() Pressing the configured shortcuts (⌘⇥ and ⌘`) results in nothing. Clicking on "Show" in AltTab's menubar icon results in nothing either. P.S. As a side note, I can confirm I'm experiencing #3801 too: even after I grant AltTab the Screen Recording permissions (as a test) and relaunch it, it still says it doesn't have them: ![]() |
I have the same issue on a Macbook 13 - Sequoia 15.0.1 👍 |
On your screenshots, the configured shortcuts use |
@lwouis on my side, I tried with both shortcuts (with ⎇, or ⌘), but without success (and I just tried again, still no success). |
Could someone please share a video of the issue? I don't have any hint on why this happens on your setups. Watching a full screen recording may show a hint of what's going on. |
@lwouis I, of course, made a mistake when writing that comment - meant ⌥⇥ and ⌥`. Pressing ⌘⇥ and ⌘` naturally activate built-in app switcher and cycle through current app's windows, respectively :). I'll try to record a video. Although I honestly don't think it will help, there's really nothing special happening, won't give you any more insight than what I've written and the screenshots provided. Maybe I could provide some logs when trying to perform these actions? Any instructions on how to do that would be great. |
@lwouis I recorded a 90s video, showing setting AltTab from scratch, from first launch, with all settings erased prior to that, and only granting it Accessibility permissions, but not Screen Recording permissions, where you can clearly see it's not working - but as soon as I give it Screen Recording permissions it does. Unfortunately, it's ~300MB, and GitHub won't allow anything bigger than 10MB. |
@michkozak you can upload it on Youtube as unlisted. You can also upload to Google Drive, iCloud, etc, and share the link here 👍 |
@lwouis Here's the video on YouTube. |
Thank you @michkozak! At 0:58 in your video, I note something unusual: when you click on the toggle to grant AltTab permission, the toggle acts strangely. Did you perhaps double-click it? Then, we see the pop up asking to restart AltTab. It pops up twice in a row. When the second pop up appears, we see clearly that AltTab is no longer visible in the menubar. What is being quit then? I've tried to double-click the toggle, and uncovered a macOS bug. See this video. I must say this Screen Recording permission was introduced by Apple in Catalina, and has been nothing but a buggy mess every since. It makes me sad to work on it, and debug these cases. It's such a mess. It should be a binary toggle. Every user should get the same experience. Anyway, I can't reproduce the double popup you got. That one is the only thing that I think could help us get to the root cause. Why on Earth do you get 2 popups in a row? Are you sure you don't have 2 instances of AltTab running at once perhaps? This looks weird as well: then You can type "AltTab" in ActivityMonitor to confirm how many instances are running. |
Ok, so 😁:
I didn't double-click it. That's just the "standard" (as in: buggy) behavior of the "reimagined" System Settings in Ventura. Not sure about Sonoma and Sequoia, if things improved, but the new System Settings they introduced in Ventura is much more buggy, much less reliable than the System Preferences up until and including Monterey. And lots, lots of quirky UI glitches just like this one. I've seen this happen many times, since the first day I upgraded to Ventura. Sometimes it works as expected. Sometimes it takes a second to register the click and then it is reflected in the UI. Sometimes once the UI catches up and the toggle changes state - it does the thing you saw in the video; looks like it was clicked twice, it goes from off to on to off to on. And sometimes it doesn't register the click at all - and you have to click a second time to get it to work. Anyhow, in that video, I only clicked once. That was just bad luck, it just happened to glitch when I was recording. Before recording the video, when I was messing around with AltTab, trying to get it to work - there were no glitches, but still the app wouldn't work without Screen Recording permissions. More importantly, that glitch was when granting the Screen Recording permissions, which I did only to demonstrate that then the app works. But the problem here is that it should work without it, with only Accessibility permissions granted, as the app itself states, giving you the option to check "Use the app without this permission".
It pops up twice in a row because of the glitch mentioned above. I only clicked once, but it somehow registered it twice, so the toggle switched state twice and presumably a call to an API was made twice too - so two subsequent popups. The first Quit & Reopen restarted the app and it disappeared from the menubar. The second Quit & Reopen either (a) made an API call but it failed, since the app was not yet launched, or (b) restarted it again - the process was probably alive, but it was not yet reflected in the UI, meaning no icon in the menubar.
I agree. The expanded permissions system introduced in Catalina was and is nothing but pain.
I'm sure, there's only one AltTab process running. What you see there is standard Bartender behavior. I only have some icons always visible in the system's menubar, and the rest semi-hidden in the second bar (Bartender's), that stays hidden until explicitly summoned. When you have an icon in the secondary, Bartender's bar, if you activate it, it shows up in the system's menubar where you can interact with it - but it doesn't disappear from the Bartender's bar. Also, when you launch an app, majority of time it first shows up in the system's menubar, then Bartender catches up and it shows up in its bar as well. And that's the behavior you're seeing in the video. Hope this clears things up. Anyway, I'm happy to record video again, without that glitch, to prove that it doesn't matter. Or do anything else that might help you diagnose it, I'm open to suggestions :). |
Hi, Could you please run this local build in Terminal.app and share the output here? In particular, the output while you're pressing the shortcut and nothing happens. Also, the output when you click "Show" in the menubar dropdown. Thank you 🙇 |
I have the same problem (coming from #3770).
Here is the output I got with the permission disabled and no popup showing at all (I removed AltTab and then installed the local build instead and then ran
Does that help?
I’m not sure if it happens exactly when pressing the shortcut or clicking "Show", as this I tried when the permission is granted (and AltTab works), and there I get similar but slightly different messages:
I’m not sure how to understand this output, but hopefully it helps. |
Thank you @guillaumebrunerie! I narrowed the issue down thanks to your logs. AltTab doesn't show because it thinks MissionControl is active (e.g. Expose is showing). For some reason, this heuristic triggers when AltTab has no permission, I think. Could you please run this new local build and share the logs? AltTab is not granted Screen Recording Permission, then:
Thank you 🙇 |
Did a clean reinstall. Here's my output when pressing the shortcut:
For whatever reason, it's not outputting anything when I click on Show in the menubar dropdown. |
Once again, after a clean reinstall, using the new build:
Strange, but tried it multiple times, same result. Hopefully, @guillaumebrunerie will have better luck. |
I did get some output with the new build. At 10:41:30 I pressed the shortcut twice, and at 10:41:45 I clicked "Show" twice.
|
This was without Mission control active, trying to use AltTab normally. Pressing the shortcut once when Mission control is active (F3, showing a mosaic of all open apps and windows) gives the following output:
|
I can confirm the same issue with macOS 15.1. As soon as I remove the permission, the app no longer works as desired. If the permissions are given, everything is ok. |
Hi everyone, I'm surprised by @guillaumebrunerie's logs. I've implemented the what yabai does for Mission Control. They have found private notifications we can use. It's working on my local machine. I think this may solve the problem for users on macOS >= 12. Here's a new local build. Could you please try it out? If I'm correct it should fix the issue for all of you. Also, could you please share logs of an invocation with mission control active and one with mission control inactive? Thank you 🙇 |
The new build works for me, Accessibility permissions granted, Screen Recording Permissions denied. Output when Mission Control is not active:
Output when Mission Control is active:
|
I tried the new local build and it all seems to be running perfectly. This time also without the rights for screen recording. Great job. Thanks |
# [7.3.0](v7.2.0...v7.3.0) (2024-11-10) ### Bug Fixes * better handle screen or space changes (closes [#1254](#1254), closes [#2983](#2983)) ([3c4aaf5](3c4aaf5)) * potential issues with key repeats due to concurrency ([4cfe16a](4cfe16a)) * switcher would not close, or cycle on its own (closes [#3117](#3117)) ([d430f83](d430f83)) * works without screen-recording permissions (closes [#3819](#3819)) ([f7de2bb](f7de2bb)) ### Features * can pass the --logs= flags at launch to show logs ([81eb07e](81eb07e)) * improve el, fi, hi, it, pl, pt localizations ([a9614c1](a9614c1))
Just updated to 7.3.0 via the Check for Updates menu, and turned off screen recording permissions. Thank you! ❤️ |
@lwouis That's what I should have said in my last comment, too: thank you 🙏🏻. |
I decided to spend some time on this again and finally got it working on Sequoia 15.1.1. My installation is via Homebrew, so your re-installation method may be different (and maybe unnecessary), but this got me going again on 3 separate 15.1.1 arm64 Macs. Most of this is not new, but deleting the preferences, et al. seemed to be what specifically got Alt-Tab running again for me:
After going through the permission dialogues and granting the appropriate access, Alt-Tab began working for me again across 3 separate 15.1.1 Macs. (I'm fine granting Alt-Tab screen recording permsissions.) |
I don't want to give AltTab permissions to record my screen, I don't need it to show me window thumbnails, I'm perfectly fine with just icons and titles. However, if I don't grant it that permission - the app simply doesn't work. Nothing pops up when I press the configured keyboard shortcuts. As soon as I grant the app Screen Recording permission - everything works fine.
Mind you, this is with Use the app without this permission. Thumbnails won't show checked and Appearance set to App Icons. Accessibility permission is, of course, granted.
AltTab 7.2.0 running on Ventura 13.7.1, M1 MacBook Air.
P.S. Now that I'm writing this, I remembered that this was the case a good while back. Someone recommended AltTab to me, I downloaded it to try it out and at that time I didn't want to grant it the Screen Recording permission too - and the app didn't work. I think I was on Monterey at that time.
P.P.S. Sorry for duplication, I first sent this as an in-app feedback.
The text was updated successfully, but these errors were encountered: