Tokoroflow Posted Thursday at 03:38 PM Posted Thursday at 03:38 PM (edited) I’m unable to get it to work. Here’s a partial log, but I can’t post the entire thing, might be too long… Quote 17 errors generated. <unknown>:0: error: failed to emit precompiled header '/var/folders/xh/7dfjpy8d1f971n8z7__s_z0c0000gn/T/TemporaryDirectory.sQe12H/AccessibilityBridgingHeader.pch' for bridging header 'src/AccessibilityBridgingHeader.h' src/AccessibilityBridgingHeader.h:11:9: error: could not build module 'AppKit' 9 | #define AccessibilityBridgingHeader_h 10 | 11 | #import <AppKit/AppKit.h> | `- error: could not build module 'AppKit' 12 | 13 | AXError _AXUIElementGetWindow(AXUIElementRef element, uint32_t *identifier); ./src/AccessibilityBridgingHeader.h:13:55: error: unknown type name 'uint32_t' 11 | #import <AppKit/AppKit.h> 12 | 13 | AXError _AXUIElementGetWindow(AXUIElementRef element, uint32_t *identifier); | `- error: unknown type name 'uint32_t' 14 | 15 | #endif /* AccessibilityBridgingHeader_h */ Edited Thursday at 03:41 PM by Tokoroflow edit
zeitlings Posted Thursday at 07:43 PM Author Posted Thursday at 07:43 PM Perhaps try what worked here: I.e., install the Xcode command line tools, perhaps remove and re-install them, you can also try installing Xcode from the Appstore if that doesn't work. Tokoroflow 1
Tokoroflow Posted Thursday at 08:49 PM Posted Thursday at 08:49 PM 1 hour ago, zeitlings said: Perhaps try what worked here: I.e., install the Xcode command line tools, perhaps remove and re-install them, you can also try installing Xcode from the Appstore if that doesn't work. I tried reinstalling the CLT as instructed, but I get the same bugs... I sent the full log to you via PM. I hope it is useful if you are interested in taking a look. Thank you for your awesome workflows. zeitlings 1
vitor Posted Friday at 12:26 AM Posted Friday at 12:26 AM 3 hours ago, Tokoroflow said: I sent the full log to you via PM. Contacting via PM is generally worse, because no one else can collaborate and help with an insight. Plus, future people with the problem don’t benefit from the resolution or steps, if any. Public discussion has a better chance at a fix and doesn’t put all the burden on one person.
achen81 Posted Friday at 04:47 AM Posted Friday at 04:47 AM (edited) Hi, downloaded the workflow and looks promising! Something that I noticed is the `ww` command is quite slow it'll say "Gathering windows" for 2-3 seconds. This seems weird to me because `ws` command is instant. Is there expected or is there something broken? Thanks! Edited Friday at 04:48 AM by achen81
Tokoroflow Posted Friday at 07:20 AM Posted Friday at 07:20 AM 6 hours ago, vitor said: Contacting via PM is generally worse, because no one else can collaborate and help with an insight. Plus, future people with the problem don’t benefit from the resolution or steps, if any. Public discussion has a better chance at a fix and doesn’t put all the burden on one person. You are right, but I tried pasting the log here, but I kept getting a "banned error" when I submitted. I also tried attaching the log, but only images are accepted. I tried sending an image with the log but it was "too big". Ultimately, I caved and sent it directly to him. How can I post the log? I reckon I am not very versed in these forums’ tech.
Tokoroflow Posted Friday at 07:22 AM Posted Friday at 07:22 AM 2 hours ago, achen81 said: Hi, downloaded the workflow and looks promising! Something that I noticed is the `ww` command is quite slow it'll say "Gathering windows" for 2-3 seconds. This seems weird to me because `ws` command is instant. Is there expected or is there something broken? Thanks! That is the same behavior I observe, I you check the workflow logs when you try to execute it you might be getting the same error as me
zeitlings Posted Friday at 08:02 AM Author Posted Friday at 08:02 AM 3 hours ago, achen81 said: Hi, downloaded the workflow and looks promising! Something that I noticed is the `ww` command is quite slow it'll say "Gathering windows" for 2-3 seconds. This seems weird to me because `ws` command is instant. Is there expected or is there something broken? Thanks! Hey, that's due to a necessary compromise. Check the release note: 23 hours ago, zeitlings said: v2.0.0 Rewrite to compensate for the deprecation of CGWindowListCreateImage in macOS 15 Side-effect: Minimized windows are now also shown The rewrite heavily relies on the Accessibility API. This results in a less performant version of the workflow, which is compensated with caching as much as possible. If you're already using a previous version of the workflow compiled before macOS 15, you can safely skip this update. Previously, getting the windows globally was very fast due to a validation approach that used CGWindowListCreateImage, a function that has been made inaccessible in macOS 15. The new validation approach is way more involved and uses the Accessibility API, which is slower. It's not broken, but a compromise to still be able to have global switching functionality. ws uses a different approach that is available for windows that are on the current desktop space (and only those) and is way faster. It's the same approach that the other window switchers are using. 11 hours ago, Tokoroflow said: I tried reinstalling the CLT as instructed, but I get the same bugs... I sent the full log to you via PM. I hope it is useful if you are interested in taking a look. Thank you for your awesome workflows. Thanks for sending those. They confirm my suspicion, that it's about SwiftBridging again, which has been causing a lot of trouble since macOS 15 came around. The solution I linked above worked for @JoelC, and it's the best I currently have to offer. If that doesn't work for you, then I don't know what else can be done at this time 🤷♂️ Tokoroflow 1
vitor Posted Friday at 10:56 AM Posted Friday at 10:56 AM 3 hours ago, Tokoroflow said: How can I post the log? If it’s that big, you can use something like https://pastebin.com which will allow you to paste it there (free; no account necessary) and get a link. 14 hours ago, Tokoroflow said: I tried reinstalling the CLT as instructed, but I get the same bugs Could you describe the exact steps you took? How exactly did you uninstall the old one? Where did you get the new one? How did you install it? Also, do you have Xcode installed? If so, what version and from where (Mac App Store or website)? There is some nuance to it when it gets fixed for people, so I’d like to understand exactly what people are doing to detect the universal fix. Tokoroflow 1
Tokoroflow Posted Friday at 07:45 PM Posted Friday at 07:45 PM (edited) 8 hours ago, vitor said: If it’s that big, you can use something like https://pastebin.com which will allow you to paste it there (free; no account necessary) and get a link. Could you describe the exact steps you took? How exactly did you uninstall the old one? Where did you get the new one? How did you install it? Also, do you have Xcode installed? If so, what version and from where (Mac App Store or website)? There is some nuance to it when it gets fixed for people, so I’d like to understand exactly what people are doing to detect the universal fix. Certainly, thanks 😁 I used sudo rm -rf /Library/Developer/CommandLineTools/ and xcode-select --install" to install to install I didn't try the App Store install since I am unsure if I am going to break more things using two different install sources for the same thing. Correct me if I am wrong. I am pretty new to macOS. Also, Full log Error log Edited Friday at 07:47 PM by Tokoroflow
vitor Posted Friday at 08:52 PM Posted Friday at 08:52 PM But do you have Xcode at all? I mean the big GUI app, not just the command-line tools. To be clear, you don’t need to have it I’m asking to better understand your set up. What are the outputs of these two commands? xcode-select --version xcode-select --print-path After you get those, remove the command-line tools again, with the sudo rm command as you did before and install them from the PKG located at https://download.developer.apple.com/Developer_Tools/Command_Line_Tools_for_Xcode_16.2/Command_Line_Tools_for_Xcode_16.2.dmg. Doing that manual install is what’s been working for some people. You’ll probably need to log in with your Apple Account for that link to work. Tokoroflow and zeitlings 2
Tokoroflow Posted Saturday at 12:28 AM Posted Saturday at 12:28 AM 3 hours ago, vitor said: xcode-select --version -> xcode-select version 2409. xcode-select --print-path -> /Library/Developer/CommandLineTools I added the results. ty
vitor Posted Saturday at 12:21 PM Posted Saturday at 12:21 PM That looks OK. Have you done the other steps of removing and installing from the PKG?
Tokoroflow Posted Saturday at 12:32 PM Posted Saturday at 12:32 PM (edited) 11 minutes ago, vitor said: That looks OK. Have you done the other steps or removing and installing from the PKG? Should I remove Xcode with: sudo rm -rf /Library/Developer/CommandLineTools/ and later install it via the AppStore? Edited Saturday at 12:33 PM by Tokoroflow
vitor Posted Saturday at 12:46 PM Posted Saturday at 12:46 PM No, not the AppStore, use the link I posted.
Tokoroflow Posted Saturday at 02:24 PM Posted Saturday at 02:24 PM 1 hour ago, vitor said: No, not the AppStore, use the link I posted. Success. So downloading Xcode from apple website, uncompressing the Xcode app inside the applications folder fixed the issue. Thanks to everyone for the help. zeitlings 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now