MacOS Sequoia 15.0 Compatibility

[kaiwalyajoshi]

MacOS Sequoia was released today, has anyone tried it out with Aerospace?

I'm holding off on the MacOS upgrades incase there are any bugs with Aerospace.

[diogox]

Same here. Who will take one for the team? 👀

[sashaaldrick]

I just upgraded without even thinking about Aerospace as I'm so used to it 😅 as far as I can tell everything works great.

[diogox]

Can confirm, so far so good 🙌

[Alienover]

Anyone used alt + number to focus workspace?
e.g.:

alt-1 = 'workspace 1'
alt-2 = 'workspace 2'
alt-3 = 'workspace 3'
# ...

I got those special characters no matter in kitty or mac built-in terminal.

But outside the terminal app, it works well as before.

---

FYI

macOS Sequoia:  Version 15.0 (24A335)

Aerospace Version:
  aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
  AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

---

Updated at 2024/09/17 13:57 PDT

Fixed it by disabling secure keyboard entry
cc @sashaaldrick @lampewebdev

[lampewebdev]

for me super + [anything] stopped working and shift + super + [anything] also stopped working. So I can not move around anything to a new workspace in aerospace

Okay it only does not work when I'm focused on kitty terminal for some reason

[sashaaldrick]

Anyone used alt + number to focus workspace? e.g.:

alt-1 = 'workspace 1'
alt-2 = 'workspace 2'
alt-3 = 'workspace 3'
# ...

I got those special characters no matter in kitty or mac built-in terminal.

But outside the terminal app, it works well as before.

FYI

macOS Sequoia:  Version 15.0 (24A335)

Aerospace Version:
  aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
  AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

I use alt + number for workspaces and everything works on my end just as before. Same for shift + alt for sending a window to that workspace.

Same exact builds for macOS and Aerospace:

sw_vers
ProductName:		macOS
ProductVersion:		15.0
BuildVersion:		24A335

aerospace --version
aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

[lampewebdev]

Anyone used alt + number to focus workspace? e.g.:

alt-1 = 'workspace 1'
alt-2 = 'workspace 2'
alt-3 = 'workspace 3'
# ...

I got those special characters no matter in kitty or mac built-in terminal.
But outside the terminal app, it works well as before.
FYI

macOS Sequoia:  Version 15.0 (24A335)

Aerospace Version:
  aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
  AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

I use alt + number for workspaces and everything works on my end just as before. Same for shift + alt for sending a window to that workspace.

Same exact builds for macOS and Aerospace:

sw_vers
ProductName:		macOS
ProductVersion:		15.0
BuildVersion:		24A335

aerospace --version
aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

try to focus kitty terminal and then to do the shortcuts this is where it breaks for me also. If not then it is something in the kitty config.

[GreenRuslan]

I have one issue that was not present on Sierra.

I use the Arc browser as the default. Also, I use their feature, which opens new links in the so-called "small browser," which can be closed if you don't want to open this link in the main space.

Steps to reproduce:

• open Arc browser in the space
• open any link in a small browser (I open links from the messenger which is float mode)
• close small browser

Actual result
The empty space that was occupied by the small browser stays, and the main browser window is not resized. The empty space after the small window is closed is still registered as a window, and I can switch to it.

Expected result
The small browser is closed, and the main browser window is resized.

[GreenRuslan]

Adding info to my previous message - when it happens, It stops going to the messenger window, which is in float mode. I can jump only to the empty space, which stays after the small browser window is closed and the main window. When I restart the browser - everything works as it should.

[aaftre]

i'm having issues on sequoia with aerospace resizing existing windows after a window on a desktop is closed. similar to @GreenRuslan's post. also using arc, but other apps might be affected as well.

[ezhang7423]

I am getting the same error as @GreenRuslan and @aaftre . When I close a window, the remaining windows don't take up the empty space. As a result, I have a whole host of empty space which grows larger with each window that close.

[junereycasuga]

mine had no issues. focusing to other window from kitty had no problems as well.

ProductName:            macOS
ProductVersion:         15.0
BuildVersion:           24A335

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

[jalet]

Had no issues as well

15.0 (24A335)

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

[tuzemec]

This is interesting: p0deje/Maccy#872
It seems that Apple is kinda restricting global shortcuts with only option as a modifier in Sequoia.
And by "interesting" I mean "wtf?".

Can anyone confirm this?

[tkivela]

Option key shortcuts work with macOS 15.0 & Aerospace fine atleast for me.
But can confirm that there's is a bug with resizing (the one that ezhang7423 mentioned)

[shrimpram]

Re: the close window/resizing issue that a few have mentioned, a workaround I've found is that using aerospace close (see docs) to close a window ensures that the remaining windows are resized to take up any empty space. I've bound this to alt + w for convenience.

[mhesham32]

I'm getting an issue for the tab I specified apps to launch on it. like the c tab chrome starts on it as a single window then I specify the profile to use. the opened profile window will use half of the screen despite that no other windows exist there if I closed this window and opened another app it will use third of the screen as if there are two other windows opened but that's not the case

[nikitabobko]

I am getting the same error as @GreenRuslan and @aaftre . When I close a window, the remaining windows don't take up the empty space. As a result, I have a whole host of empty space which grows larger with each window that close.

@GreenRuslan @aaftre @ezhang7423 please check if you have any other apps that use macOS accessibility API #471 (comment) (System Settings -> Privacy & Security -> Accessibility)

[BasilPH]

@GreenRuslan @aaftre @ezhang7423 please check if you have any other apps that use macOS accessibility API #471 (comment) (System Settings -> Privacy & Security -> Accessibility)

I have the same issue, and I have a couple of apps that use macOS accessibility. Notably, I also use Contexts, which someone mentions in #471. Not using Contexts fixes this issue for me. However, it would be nice if I could keep using it.

[aaftre]

I am getting the same error as @GreenRuslan and @aaftre . When I close a window, the remaining windows don't take up the empty space. As a result, I have a whole host of empty space which grows larger with each window that close.

@GreenRuslan @aaftre @ezhang7423 please check if you have any other apps that use macOS accessibility API #471 (comment) (System Settings -> Privacy & Security -> Accessibility)

[johnnyBira]

I updated to Sequoia today and installed AeroSpace for the first time.
For me almost none of the keybindings are working.

Also (and possible unrelated to the OS update) it seams like there are some kind of keybinding to the square and curly bracket keys. It's unclear to me what they are, since there is no sign of such a mapping in the config. I'm not able to output these keys ([, ], {, }) since they seam to be "blocked"/used by AeroSpace somehow.

[GreenRuslan]

I am getting the same error as @GreenRuslan and @aaftre . When I close a window, the remaining windows don't take up the empty space. As a result, I have a whole host of empty space which grows larger with each window that close.

@GreenRuslan @aaftre @ezhang7423 please check if you have any other apps that use macOS accessibility API #471 (comment) (System Settings -> Privacy & Security -> Accessibility)

Here is the the list of apps:

[ecosse3]

I've updated to MacOS Sequoia 15.0 and Aerospace is pretty unusable now due to how it manages windows in virtual workspace. When I have one window only it still creates space for another and it seems broken. I need to use fullscreen for each app to be able to work with Aerospace.

Here is how I can move window by keybinding:

cmd-alt-shift-j = 'move down'
cmd-alt-shift-k = 'move up'

I'm using layout tiles horizontal vertical. accordion layout seems to work fine.

AerospaceIssue.mp4

[ezhang7423]

@nikitabobko

[ezhang7423]

Do we have any updates on this?

[nikitabobko]

I'm on Sequoia for the last few days and I see no regressions. Individual bugs must be reported as separate issues

The bug that some closed windows still take space is somehow related to using other apps like contexts app. I don't use contexts app, and I don't know what is the cause, other apps may also affect this (most probably they use accessibility api). But I think the fix suggested in this issue #445 will fix the bug.

This is interesting: p0deje/Maccy#872
It seems that Apple is kinda restricting global shortcuts with only option as a modifier in Sequoia.
And by "interesting" I mean "wtf?".

In macOS 15, Apple doesn't allow to capture hotkeys with opt and opt+shift modifier but it only affects sandboxed apps. AeroSpace is not a sandboxed, that's why it's not affected. AeroSpace needs to access accessibility API anyway, which is not available in sandbox.

But it is sad to see Apple going in this directioon https://developer.apple.com/forums//thread/763878?src=push&answerId=804374022#804374022

[ezhang7423]

Hi @nikitabobko, what is the fix suggested in #445? I read through the issue and did not find anything concrete.

[ianmartorell]

@ezhang7423 I was experiencing the same issue with closed windows not being detected by Aerospace and after deactivating every other app in Accessibility under System Settings and rebooting, it hasn't happened again. From your list I see the ones we had in common are Raycast and skhd, although skhd I had already uninstalled. So I would suggest disabling Raycast (or everything) and rebooting to see if it that helps.

[Kikangh]

Hi, if you don’t mind me asking, did you enable the applications after that in accessibility settings or not ? I am not yet under sequoia, and won’t upgrade until I can « safely » use all my applications, including Raycast and Aerospace, and I have quite a few applications needing accessibility setting enabled. Le 24 sept. 2024 à 18:51, Ian Martorell ***@***.***> a écrit : @ezhang7423 <https://github.com/ezhang7423> I was experiencing the same issue with closed windows not being detected by Aerospace and after deactivating every other app in Accessibility under System Settings and rebooting, it hasn't happened again. From your list I see the ones we had in common are Raycast and skhd, although skhd I had already uninstalled. So I would suggest disabling Raycast (or everything) and rebooting to see if it that helps. — Reply to this email directly, view it on GitHub <#514 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZPRL27SABZQ4JOL4LT2ITZYGJ7RAVCNFSM6AAAAABOJY423GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRHAZDEMJVGU>. You are receiving this because you are subscribed to this thread.

[ianmartorell]

Hi, if you don’t mind me asking, did you enable the applications after that in accessibility settings or not ? I am not yet under sequoia, and won’t upgrade until I can « safely » use all my applications, including Raycast and Aerospace, and I have quite a few applications needing accessibility setting enabled.

I've enabled back Logi Options+ and Raycast and no issues so far. Enabling Amazon Q did bring back the issue so I turned it back off, and I haven't felt like I'm missing anything else so far.

[ezhang7423]

Unfortunately, disabling all my other applications in the Accessibility settings still did not fix the issue @ianmartorell . Would be extremely grateful for your help @nikitabobko, as my workflow has been largely disrupted at this point.

[mhesham32]

Thanks @ianmartorell AmazonQ was the issue for me as well after disabling its access I got Aerospace working as before

[Kikangh]

Thanks Le 24 sept. 2024 à 20:53, Ian Martorell ***@***.***> a écrit : Hi, if you don’t mind me asking, did you enable the applications after that in accessibility settings or not ? I am not yet under sequoia, and won’t upgrade until I can « safely » use all my applications, including Raycast and Aerospace, and I have quite a few applications needing accessibility setting enabled. I've enabled back Logi Options+ and Raycast and no issues so far. Enabling Amazon Q did bring back the issue so I turned it back off, and I haven't felt like I'm missing anything else so far. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[whkoh]

Really tough to choose between contexts and aerospace. Are there any workarounds that still allow me to use contexts?

[haveanicedavid]

As a workaround, binding a key to the 'close' command, ie alt-x = 'close' avoids the phantom windows.

I use both contexts and amazon q, so hoping there's a fix for this :D

[aintyourcupoftea]

Amazon Q is causing the issue for me. I uninstalled it and the issue was solved. But I wish to keep using Amazon Q!
I really wish this issue is fixed.
For now I am using @haveanicedavid workaround of adding alt-x='close' in my aerospace.toml but this way also it glitches sometimes.
I have also created a automator shell script :
pkill -f AeroSpace open -a "AeroSpace"
and then assigned a keyboard shortcut for this script to run. Whenever I face this issue (which is like very often), I use the keyboard shortcut to restart aerospace and it starts working again.
But, it's my request to developers to please fix this issue! I will be really grateful.. thank you.