Space Creation Doesn't Work on 26.4

[wiggly-sheets]

Updated to the official release of 26.4 last night and noticed this morning that I can’t create a new space using my existing scripts, nor from the command line using yabai -m space --create. All other features are working from what I can tell, including moving windows from one space to another, so I don't believe it's an issue with skhd nor has my setup changed in the interim. I also tried reloading the scripting addition and making sure that it was up to date.
Edit: Using yabai from head yabai-v7.1.17
Edit 2: Space destruction does work
Edit 3: Moving spaces forward and back as well as to specific indices also does not work.

[m4r1vs]

Does not work for me either. The CLI command "fails" silently (exits 0 OK). I noticed that sudo yabai --load-sa returns error code 1 and I don't get the notification that the scripting addition has been loaded. However, I'm pretty sure it is because I can switch spaces and move windows from one to another using yabai.

[wiggly-sheets]

Does not work for me either. The CLI command "fails" silently (exits 0 OK). I noticed that sudo yabai --load-sa returns error code 1 and I don't get the notification that the scripting addition has been loaded. However, I'm pretty sure it is because I can switch spaces and move windows from one to another using yabai.

SA seems to be working for me as transparency, animations and other SA-dependent features are working. Must have been a change in 26.4 with space management.

[stephen-zeng]

+1, mine doesn't work on creating space either. But yabai -m space --focus next and yabai -m space --focus prev works as expected on my machine.

[m4r1vs]

SA seems to be working for me as transparency, animations and other SA-dependent features are working. Must have been a change in 26.4 with space management.

Yeah, it works for me too fortunately. However, the loading command exits with an error and no notification is displayed on macos. Does sudo yabai --load-sa run as usual for you or is it also erroring?

[m4r1vs]

from #2766:

This also appears to be a macOS-level limitation, dragging the active space to another display via Mission Control no longer works either. Only inactive/unfocused spaces can be moved between displays.

Probably related? @wiggly-sheets

[Icecreambobcat]

This is almost certainly a change in the dock binary that we'll have to adjust the SA patterns for. Can anyone send a zip of their dock.app found at /System/Library/CoreServices/ along with the sha256sum of it (before the zip)? We'll be able to adjust the patterns with this new binary to compare it against. This'll probably also solve #2766 if we can find a pattern for that. Also, can anyone screenshot their console logs when filtering for yabai-sa after running sudo yabai --uninstall-sa and then restarting yabai? This'll help with determining which specific patterns need to be addressed.

[stephen-zeng]

Dock.zip

05526ac774da62905a8ddbd84b9487721bc58ce4a19516ff03004798c0dd07e0forDock.app/Contents/MacOS/Dock.
And here is the screenshot:

Hope it can help you!

[hieuvp]

Hi,
I'm running into the same issue after upgrading to macOS Tahoe 26.4. I have uninstalled yabai, uninstall sa, uninstall service, and reinstall everything in the HEAD again, but it still doesn't work.

When I enter the command yabai -m space --create, it doesn't return any error, but it also doesn't create any space.

[m4r1vs]

The new address for addSpace: 0x250000 on arm64. Works for me perfectly.

Console log: [yabai-sa] (0x1044d0000) addSpace found at address 0x10466E150 (0x19e150)

I actually somehow don't get the dppm error though on my MBP
Now I got it and fixed the arm address: [yabai-sa] (0x1006d4000) dppm found at address 0x4880D0 (0xfffffffeffdb40d0)

[m4r1vs]

m4r1vs@426e78c fixes it on arm64, however I have no access to an x86 mac so I cannot fix it for that arch. Also I have some other changes on my fork so someone else would probably be better suited to open a PR

edit: nvm, space creation works but after creating a space, the scripting addition breaks :/ I'm not smart enough to fix this

[Icecreambobcat]

For anyone interested in working on this in the meantime, the recommended workflow is linked here.

[Icecreambobcat]

Here are the new and old hex codes for the dppm pattern, respectively.

(The add space pattern is taking a bit longer to find)

[Icecreambobcat]

Icecreambobcat@6b545be should fix this. Feel free to test and let me know any issues.

[Icecreambobcat]

@asmvik should be ok for merge.

Edit: Why are PRs restricted? We should particularly look towards community contributions for rapid response updates to new MacOS versions in my opinion.