JSON error... for aerospace

[AnirudhG07]

Hi @Jean-Tinland This is continuation of #401,
Now I upgraded version from 0.15.2 to 0.16.2, now I get this error :<

I got this error now...

Please fix this. I tried going back commits, it didnt get fixed for either.

[Jean-Tinland]

Ty for the error log, it seems that the init script is failing.

You said earlier that you tried to replace the aerospace_path variable with $(which aerospace), have you cleaned up this test?

If so, can you try to go in the simple-bar root (should be /Users/{user}/Library/Application Support/Übersicht) directory and run this command:

bash lib/scripts/init-aerospace.sh "/your/aerospace/path"

And what about this command now?

aerospace list-monitors --json --format "%{monitor-id} %{monitor-appkit-nsscreen-screens-id}"

Thank you for opening this discussion, it's better to talk here than in the original issue, it must have been spamming some people. :)

[AnirudhG07]

Yes it worked! I actually deleted the aerospace installed by nixpkgs, to homebrew and this worked!
I probably didnt installed aerospace with nixpkgs properly which was causing this error.

Also I so noticed if went back the commits before rollback, It gave the error of JSON Error.... as usual.
Edit: I installed aerospace 0.16.2 from nix, NOW it works
It works even when I go to commit before rollback! (I noticed this because simple-bar worked when I deleted homebrew aerospace to nix one)

[AnirudhG07]

I'll experiment around with 2 things - homebrew aerospace + nix aerospace BEFORE rollback i.e. $(which aerospace) and after rollback(the usual and current commit)

[AnirudhG07]

Here is the status with my checks (all in latest aerospace version)

1. NIX installation

• Before and After rollback, BOTH work

2. Brew installation

• After rollback works, before one(i.e. with which aerospace) doesnt work.

so 3/4 cases work. if the 4th not working case works out for you, then great! I am anyways using nix so no need for brew

[Jean-Tinland]

Glad it worked, and thank you for this experiment! I suppose there will always be some edge case or curious bugs for some people; it's difficult to always find the source of the problem!

I'll stick to the current approach then: the user will always have to check his window manager path in case of error on first start, but at least it should work for everyone!

[AnirudhG07]

Cool.