MacOS 26.1. - Aerospace cannot be started #1794
Replies: 3 comments 4 replies
-
|
Same issue here, and there's a runtime error shown as popup with content below. AeroSpace Runtime ErrorPlease report to: Message: Stacktrace: |
Beta Was this translation helpful? Give feedback.
-
|
I've got the same issue with 0.20.0-Beta: no crash logs, no process in activity monitor. I'm on macOS Tahoe 26.1 (25B78) |
Beta Was this translation helpful? Give feedback.
-
|
Im having the same issue, it does not happen on older versions of Aerospace it seems, as my mac mini and old mbp (just got a new one today and installed Aerospace) are still working fine with it If you run aerospace and point it to a config file, you will get the crash report: ##### AeroSpace Runtime Error #####
Please report to:
https://github.com/nikitabobko/AeroSpace/discussions/categories/potential-bugs
Please describe what you did to trigger this error
Message:
Version: 0.20.0-Beta
Git hash: 1ec4234a25091225ca2442c2d37e45432dd1b347
refreshSessionEvent: nil
Date: 2025-12-06 06:14:10 +0000
Thread name:
Is main thread: true
axTaskLocalAppThreadToken: nil
macOS version: Version 26.0 (Build 25A8353)
Coordinate: AppBundle/Config.swift:8:10 getDefaultConfigUrlFromProject()
recursionDetectorDuringTermination: false
cli: false
Monitor count: 1
Displays have separate spaces: true
Stacktrace:
0 AeroSpace 0x00000001049d15cc $s6Common4dieT_4file4line6column8functionxSS_SSS2iSStlFs5NeverO_Tg5 + 2036
1 AeroSpace 0x0000000104a393b0 $s6Common5check__4file4line6column8functionySb_SSyXKSSS2iSStF + 92
2 AeroSpace 0x00000001048310f8 $s9AppBundle30getDefaultConfigUrlFromProject10Foundation3URLVyF + 532
3 AeroSpace 0x0000000104831450 $s9AppBundle16defaultConfigUrl10Foundation3URLVvg + 468
4 AeroSpace 0x0000000104831538 $s9AppBundle13defaultConfigAA0D0VvpfiADyXEfU_ + 104
5 AeroSpace 0x00000001048314ac $s9AppBundle13defaultConfig_WZ + 24
6 libdispatch.dylib 0x0000000191d2aac4 _dispatch_client_callout + 16
7 libdispatch.dylib 0x0000000191d13a60 _dispatch_once_callout + 32
8 AeroSpace 0x0000000104831798 $s9AppBundle6config_WZ + 124
9 libdispatch.dylib 0x0000000191d2aac4 _dispatch_client_callout + 16
10 libdispatch.dylib 0x0000000191d13a60 _dispatch_once_callout + 32
11 AeroSpace 0x0000000104826998 $s9AppBundle12reloadConfig4args05forceD3Url6stdoutSb6Common06ReloadD7CmdArgsV_10Foundation3URLVSgSSztYaKFTY0_ + 768
12 AeroSpace 0x0000000104826ed9 $s9AppBundle12reloadConfig05forceD3UrlSb10Foundation3URLVSg_tYaKFTQ1_ + 1
13 AeroSpace 0x0000000104856fb1 $s9AppBundle04initaB0yyFyyYaKcfU_TQ1_ + 1
14 AeroSpace 0x00000001047f84d5 $s9AppBundle14GlobalObserverO7onNotif33_F1205CFDC13498282252A689C79131F6LLyy10Foundation12NotificationVFZyyYaYbScMYccfU_TATQ0_ + 1
15 libswift_Concurrency.dylib 0x000000028a661dfd _ZL23completeTaskWithClosurePN5swift12AsyncContextEPNS_10SwiftErrorE + 1When I launch it otherwise, sometimes it launches, most of the time not, and even when it does it only uses default settings and ignores my config file (of which, is default at the moment besides gaps changes because i havent been able to customize anything) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Body
Steps to reproduce:
Expected result: Aerospace is running and working
Actual result: Aerospace does not even leave a log trace. It's like it was never started. You can start it as much as so you want but it seems to be non responsive like MacOS cannot open the app.
Beta Was this translation helpful? Give feedback.
All reactions