Throwing application to another space is broken.

[JS211]

Describe the bug
Updated to Mac OS 14.5 which caused throwing applications to different spaces to stop working and crash amethyst v0.20. Updated to amethyst v0.21 and it no longer crashes but throwing apps to different spaces still doesn’t work.
Applications:
What applications are involved?
Any application

To Reproduce
Assign a shortcut to throw current application to space 1, 2, or 3.
Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions:

• macOS: 14.5
• Amethyst: 0.20, 0.21

Debug Info

$ /Applications/Amethyst.app/Contents/MacOS/Amethyst --debug-info [--include-apps]

Note: --include-apps will list your manageable applications, but is optional if you don't want to list that.

Additional context
Add any other context about the problem here.

[joshuaalderson]

After updating to 14.5 I am also experiencing the same issue. 14 inch M3 MacBook, Amethyst Version 0.20.0 (108)

When trying to use the keyboard shortcut to send a window to another screen it sends it and then sends it back to the original display instantly. Interestingly moving the window with the trackpad to another display still seems to work however.

I've tried relaunching the Amethyst app, completely closing/quitting the app and opening again and still doesn't work. I've also tried different displays and have the same issue.

[ianyh]

Dang. I'll upgrade and give it a go. The APIs probably changed in some way.

[hpfmn]

FYI: yabai has the same issue. I would also think that something about SkyLight did change. My problem is that I don’t know much about how this framework works. I guess SLSMoveWindowsToManagedSpace is our problem here. I think you use this function as well?

[dee-kryvenko]

Got the same problem. Interesting that if I have Amethyst disabled, the key combination still makes my screen flicker and the tab bar briefly change the title of the focused screen to something else, although it happens so quick that you can't really read it. I recorded it and in the recording I can see it changes to Finder and back.

[joshuaalderson]

Just to add on to the above; when I disable Amethyst moving apps to different windows using the keyboard shortcut actually works? Perhaps this is obvious to others but I thought disabling Amethyst would disable this functionality. Of course the windows margin stuff doesn't work but at least for now I can get the keyboard shortcuts working to move app windows to different screens

[phrmendes]

Same problem here. Also, I believe that this issue is related to this bug.

[porkloin]

+1, I have one machine on 14.4.1 with no issues, another on 14.5 where I can no longer throw windows to other spaces, exact same config otherwise.

[porkloin]

FWIW, it seems like the yabai folks found a temporary solution: koekeishiya/yabai#2240 (comment)

Bad news is that it looks like the API change may require SIP to be disabled, which is a huge problem for people working on employer-owned hardware that can't be modified like that. 😬

[ianyh]

Yeah, I'm not particularly surprised, honestly. Seemed like a matter of time before the private APIs got locked down. If history is any indication, Apple will probably lock it down and then immediately launch their new tiling window manager, macOS Flow or something. 😂

I'll try to apply yabai's fix for now, and hope for the best.

[kolchurinvv]

Raycast's window management is still intact. throwing to next display and to next desktop works just fine somehow on 14.5

[Ryan-the-hito]

Raycast's window management is still intact. throwing to next display and to next desktop works just fine somehow on 14.5

For me, Raycast is also dead. It can only move its own Setting window but leaves other windows still.

[kolchurinvv]

@Ryan-the-hito - i double checked and you're right. it was able to throw a focused window to the next display, but that could be related to the fact the the dock i'm using requires display link software. when unplugged from the dock raycast behaves exactly like you describe

[escherlies]

Same problem here. Also, I believe that this issue is related to this bug.

I think too, i noticed the thrown window looses focus which makes it broken.

Also FYI, I just rolled back to Amethyst v0.20.0 (108) and everything's working fine again.

EDIT: Still using MacOS 14.4.1

[svrdlans]

Also FYI, I just rolled back to Amethyst v0.20.0 (108) and everything's working fine again.

I tried going back to v0.20.0 on Sonoma 14.5, it allows me to throw window between screens (laptop - monitor), but doesn't seem to be aware of Spaces and can't throw window to different Spaces on the same screen

for now I drag-drop to specific Spaces ¯_(ツ)_/¯

[Ryan-the-hito]

@svrdlans I tried the latest BetterTouchTool and it is still working. I guess it uses a different way to send windows to different spaces. So now I am assigning the original shortcuts in the BetterTouchTool. 😀

[escherlies]

Also FYI, I just rolled back to Amethyst v0.20.0 (108) and everything's working fine again.

I tried going back to v0.20.0 on Sonoma 14.5, it allows me to throw window between screens (laptop - monitor), but doesn't seem to be aware of Spaces and can't throw window to different Spaces on the same screen

for now I drag-drop to specific Spaces ¯_(ツ)_/¯

Ah thanks for clarification!

I am still on 14.4.1... So I think I'll wait for the update 😅

[denisbr]

Apparently yabai was able to restore space throwing functionality?
koekeishiya/yabai#2240 (comment)

[HanSooloo]

On macOS 14.5 and after getting the 0.21 update lost ability to throw windows to spaces. When I used the shortcut key, the window flashes for a split second and doesn't move. Stays in the same screen.
When I reverted back to Amethyst 0.20, the flashing doesn't happen, but throwing to a space doesn't work either.

I wonder if this points to a macOS 14.4 ==> 14.5 issue.

[aleksozolins]

Friends it is broken for me as well. I hope for a fix soon but do not have the ability myself.

[Vinh-CHUC]

broken for me too! hoping for a fix too :)

[HanSooloo]

On a macOS 14..4 laptop I have, Amethyst 0.21 is able to throw windows.Sent from my iPadOn May 26, 2024, at 2:50 PM, Vinh CHUC ***@***.***> wrote: broken for me too! hoping for a fix too :) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[timvisher]

Please don't comment with a 'broken for me too' message. That's what the 👍 button at the top of the issue is for. Thanks in advance!

[ianyh]

Implemented the fix, which functions on 14.4.1. Need to test on 14.5 still.

[tlpierce]

If you have Keyboard Maestro, you can use a macro to throw windows between desktops as a workaround. This is what I'm currently doing. I unmapped the "Throw focused window to space..." in Amethyst preferences and mapped the same keystroke to the appropriate macro in Keyboard Maestro.

[ipstone]

@ianyh Thank you for the quick fix! - I tested it on 14.5, it works well now.

[joshuaalderson]

Thanks a lot for the quick fix - working here to on 14.5 after updating

[dfucci]

Thanks a lot for the quick fix - working here to on 14.5 after updating

How do you get the fix? I have "Get development builds" enabled, but no updates after "Check for Updates..."

[Vinh-CHUC]

@dfucci same for me, then I realised I had installed it through Homebrew needed to update through that. Maybe it's the same for you?

[Vinh-CHUC]

@ipstone @joshuaalderson in my case it doesn't work on sonoma 14.5 :(
@ianyh

I even rebooted to be sure.. Could this depend on something else also??

[pjezek]

@Vinh-CHUC I downloaded it from the release page: releases/tag/v0.21.1.
Windows lands on new space, and I am back from where I send it -> Looks like it works again.

[claviola]

@ianyh thanks for the fix! but I've noticed that this when I had Safari in full-screen somewhere, throwing a selected window still didn't work. Maybe this has always been the case, but I thought it was worth mentioning.

[Cerebus]

I have no full-screen windows and throwing with 0.21.1 and macOS 14.5 still not working for me.

[porkloin]

Just downloaded the latest Github release and throwing spaces is working great for me!

[phrmendes]

I'ts fixed for me, thanks @ianyh ❤️

[ipstone]

@ipstone @joshuaalderson in my case it doesn't work on sonoma 14.5 :( @ianyh

I even rebooted to be sure.. Could this depend on something else also??

I was on a M1 mac mini, the fix worked for me for 14.5 - did you download from the latest built?

[yougotwill]

I think the fix works on aarch64 (Apple Silicon) but not on Intel machines for some reason 🤔

[ianyh]

It could conceivably be a chip architecture thing. I can look into that, but I don't think I have access to any Intel machines at this point.

[cgrindel]

@ianyh I have an x86_64 Mac. I just built and ran Amethyst from Xcode. I see this in the log when I attempt to throw a window to another space:

18:01:45.324 ❤️ ERROR Window.move():394 - failed to set compat aside id: CGError(rawValue: -944701316)

I will do some digging. However, if you have any pointers, please let me know.

[cgrindel]

Interestingly. The raw value for the error can be different:

18:41:33.725 ❤️ ERROR Window.move():401 - failed to set compat aside id: CGError(rawValue: -1194852224)

Note: The line number keeps moving around because I added some other debug code.

[ianyh]

@koekeishiya does the compat id thing, in fact, only still work on Apple Silicon? That's so annoying.

[koekeishiya]

Works in Intel and Apple Silicon for me.

[blue-3]

same issue as @cgrindel
i have intel and apple silicon, and the fix only works on silicon for me

[ianyh]

Works in Intel and Apple Silicon for me.

Does SIP make a difference?

[simonbernard-shopify]

On Sonoma 14.5 and running Amethyst 0.21.0 (110) and I can't throw windows to other spaces. I can throw them to external monitors though.

Edit: Actually nevermind, downloading the latest patch from https://github.com/ianyh/Amethyst/releases fixed it. Thanks @ianyh!

[ja-versent]

@ianyh i don't have SIP disabled on my intel mac if that's the differentiator
i can try and get debug logs later to try illuminate the issue

[ianyh]

That's a good definitive datapoint thank you.

[claviola]

I also have access to a Mac on Intel and can try to repro later if you need more data.

[Cerebus]

I suggest @ianyh lock this issue and direct over to #1655.