on Sonoma 14.5 moving window to space is not working

[FabioLissi]

typing yabai -m window --space 2 --focus doesn't yield any results. SIP is disabled. config:

yabai -m signal --add event=dock_did_restart action="sudo yabai --load-sa" sudo yabai --load-sa

global settings

yabai -m config mouse_follows_focus on yabai -m config focus_follows_mouse on yabai -m config window_placement second_child yabai -m config split_ratio 0.50 yabai -m config mouse_modifier alt yabai -m config mouse_action1 move yabai -m config mouse_action2 resize

general space settings

yabai -m config layout bsp yabai -m config top_padding 5 yabai -m config bottom_padding 5 yabai -m config left_padding 5 yabai -m config right_padding 5 yabai -m config window_gap 5

echo "yabai configuration loaded.."

disable soecific apps

yabai -m rule --add app="^System Settings$" manage=off yabai -m rule --add app="^Calculator$" manage=off yabai -m rule --add app="^Finder$" manage=off yabai -m rule --add app="^Messages$" manage=off yabai -m rule --add app="^Obsidian$" manage=off

borders active_color=0xF0BE8900 inactive_color=0xff494d64 width=3.0 style=round hidpi=on&

[mickaelperrin]

It looks like you're missing:

yabai -m rule --apply

[pupbrained]

Same issue here, tried reinstalling yabai from HEAD but no luck. Attempting to move a window to another workspace causes it to simply just un-tile until I switch away from that workspace and back.

[FabioLissi]

yabai -m rule --apply

Where should I put this? typing yabai -m window --space 2 --focus; yabai -m rule --apply doesn't yield any results, same for: yabai -m window --space 6 --focus --apply

Also did this change lately? in the past typing this: > yabai -m window --space 2 --focus, wass enough to move window to a different space and move the focuse to it.

[berrabe]

same issue here, in previous macos version (13.x.x) i can use yabai without disable the SIP partially, everything works flawlessly especially window movement between spaces. But now in 14.5 window mode always failed to move windows between spaces

[basanys]

Same issue here after upgrading to 14.5

[mattfloat]

Possible duplicate of #2261

[drapergeek]

I'm seeing the same thing after upgrading to 14.5, with no config changes. FWIW I also downloaded and tried out Amethyst and they seem to be having the same problem.

[Sang-it]

Just updated having the same issue.

[phil-swiftly]

Likewise, having the same issue after updating today

[hpfmn]

Amethyst now also a a bug report regarding this issue https://github.com/ianyh/Amethyst/issues/1643

[koekeishiya]

Apple did Apple things and made the function protected. Will likely require SIP to be disabled from now on.

pre 14.5:

post 14.5:

[hpfmn]

I got some questions when thinking about this issue which I posted in the discussion forum: https://github.com/koekeishiya/yabai/discussions/2274 to not spam this issue. Maybe if you have the time leave me a coment :)

[jordan-da]

Apple did Apple things and made the function protected. Will likely require SIP to be disabled from now on.

pre 14.5:

post 14.5:

that would be awful, can't really turn sip of on company laptops.. i really hope this isn't true

thanks for looking into it @koekeishiya

[xbunax]

Maybe we can use bettertouchtool to accomplish this function

[faustozamparelli]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

[rubyroobs]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

[jordan-da]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

it works with SIP enabled?

[hpfmn]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

it works with SIP enabled?

"partialy" disabled. You need to disable filesystem restrictions, debug restricitons and nvram restrictions.

(Not sure why NVRAM and FS are needed, but yeah)

[B1T3X]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

it works with SIP enabled?

"partialy" disabled. You need to disable filesystem restrictions, debug restricitons and nvram restrictions.

(Not sure why NVRAM and FS are needed, but yeah)

I have the same SIP configuration and have reinstalled from HEAD but to no avail, still facing the issue :/

[berrabe]

Apple did Apple things and made the function protected. Will likely require SIP to be disabled from now on.

pre 14.5:

post 14.5:

Is there any other / alternative way to do the "windows movement" between spaces without using XMoveWindows... function that has been protected? or is it the only way because of "apple things" @koekeishiya

[hpfmn]

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

it works with SIP enabled?

"partialy" disabled. You need to disable filesystem restrictions, debug restricitons and nvram restrictions. (Not sure why NVRAM and FS are needed, but yeah)

I have the same SIP configuration and have reinstalled from HEAD but to no avail, still facing the issue :/

Did you do all the steps explained in the Wiki? And Intel or Arm?

https://github.com/koekeishiya/yabai/wiki/Disabling-System-Integrity-Protection https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(from-HEAD)

[Vib1240n]

Installing from HEAD fixed the moving windows to different spaces for as well without changing any SIP settings.

To make this work do we have to fully disable SIP or we can add a flag to this?

csrutil enable --without fs --without debug --without nvram

@koekeishiya

Installing from HEAD fixed this for me without requiring further SIP changes

it works with SIP enabled?

"partialy" disabled. You need to disable filesystem restrictions, debug restricitons and nvram restrictions. (Not sure why NVRAM and FS are needed, but yeah)

I have the same SIP configuration and have reinstalled from HEAD but to no avail, still facing the issue :/

Installing from head fixed the issue for me as well without changing any SIP configuration.

[Sang-it]

Same for me. Installing from HEAD fixed it without issues.

[aileks]

Same for me. Installing from HEAD fixed it without issues.

Installing from HEAD did not fix this for me...

[mrala]

Same for me. Installing from HEAD fixed it without issues.

Installing from HEAD did not fix this for me...

You'll need to disable SIP using the documented process.

I think there is a bit of confusion with people saying it's working "without changing any SIP configuration." The people saying this likely already had SIP disabled. I was unable to get it working when using the standard SIP enabled configuration. After following the full steps to disable SIP and installing the HEAD version, previous functionality of moving windows to spaces has been restored.

I'm on M2 ARM hardware. Here is my SIP status:

❯ uname -m
arm64

❯ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
        Apple Internal: disabled
        Kext Signing: enabled
        Filesystem Protections: disabled
        Debugging Restrictions: disabled
        DTrace Restrictions: enabled
        NVRAM Protections: disabled
        BaseSystem Verification: enabled
        Boot-arg Restrictions: disabled
        Kernel Integrity Protections: enabled
        Authenticated Root Requirement: enabled

[aileks]

Same for me. Installing from HEAD fixed it without issues.

Installing from HEAD did not fix this for me...

You'll need to disable SIP using the documented process.

I think there is a bit of confusion with people saying it's working "without changing any SIP configuration." The people saying this likely already had SIP disabled. I was unable to get it working when using the standard SIP enabled configuration. After following the full steps to disable SIP and installing the HEAD version, previous functionality of moving windows to spaces has been restored.

I'm on M2 ARM hardware. Here is my SIP status:

❯ uname -m
arm64

❯ csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
        Apple Internal: disabled
        Kext Signing: enabled
        Filesystem Protections: disabled
        Debugging Restrictions: disabled
        DTrace Restrictions: enabled
        NVRAM Protections: disabled
        BaseSystem Verification: enabled
        Boot-arg Restrictions: disabled
        Kernel Integrity Protections: enabled
        Authenticated Root Requirement: enabled

SIP has been disabled. It was before updating and after updating. I'm on an Intel Mac for what it's worth.

[mrala]

SIP has been disabled. It was before updating and after updating. I'm on an Intel Mac for what it's worth.

Have you configured the scripting addition? Seeing anything in error logs?

[aileks]

"Payload 0x7B doesn't support this macOS version!"

That's the only error I'm getting. I've done the entire install process from scratch following the wiki about 3 times now. Everything before Sonoma 14.5 was working fine, aside from a problem I've been having that I've already created an issue for. Also, there's nothing in the error log; it's completely blank.

[uherman]

Installing from HEAD fixed it for me as well, SIP partially disabled.

[koekeishiya]

Fixed on master using parts of the old legacy workspace/spaces system that for some reason is still partially maintained in some ways, but didn't get validation added to it like the new API did. (I randomly stumbled upon these some years ago, and it still works surprisingly enough). This entire situation is just ridiculous.

When this version inevitably gets patched in the next macOS update this functionality will require SIP to be partially disabled.

Works without having to disable SIP again for now though.

[aileks]

I have SIP completely disabled and I'm still getting this "payload (0x7B) doesn't support this macOS version!" error.

[kirkegaard]

The recent fix worked for me! :) Thank you!

[tftiwnbe]

The recent fix worked for me too! :D

[calism2]

The recent fix worked for me as well, but floating windows disappear when trying to move a window to another space.

[scifisamurai]

Upgraded to 7.1.1 just now. I have SIP enabled and the recent fix worked for me. I can move windows between spaces again! Thank you koekeishiya!

[jordan-da]

Upgraded to 7.1.1 just now. I have SIP enabled and the recent fix worked for me. I can move windows between spaces again! Thank you koekeishiya!

you have sip fully enabled?

[scifisamurai]

@jordan-da yes.

$ csrutil status
System Integrity Protection status: enabled.

[janfrederickk]

I had the same issue.

But reinstalled from HEAD and now it's working fine with SIP enabled.

[moniquelive]

@jan-wacker thanks! I ended up going to loop way easier to install and customize, with no need to enable SIP... 😞

[konstantinschuette]

I'm on macos 15.0.1 with an M1 Pro using the latest yabai version 7.1.4. I don't know wich macos update caused, but I cant move windows to a space for a longer time now, at least a month. Currently when I do yabai -m window --space 2, then the window disappears. But if I switch to this space, it's not shown. If I now go back to the original space, the window pops up again.

Is this now the time where I need to disable SIP in order to keep it working as before? Edit: Now after disabling SIP and restarting my mac multiple times, it's working again. But I don't want to disable it. Is there a way around it?

[gaviag-cerebras]

Just updated and seeing the exact same as @konstantinschuette.

[konstantinschuette]

I know it's not a solution to this issue but I switched now to Aerospace. I always wanted to instantly switch between (work-)spaces, which I now can. In yabai I had to disable SIP, which wasn't an option for me

[kirkegaard]

macos 15.x is sequoia, not Sonoma