-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wechsel not working macOS Monterey #20
Comments
+1 on this issue. Blank window on Monterey. |
Unfortunately I'm unable to install Monterey on my old 2013 MBP. So it's quite hard to reproduce the issue. Could you open the Console.app and filter for "wechsel"? Maybe we are able to find some log entries which give us a clue. |
The only thing I find in Console.app is if I start streaming, then attempt to open the wechsel via keyboard shortcut. I've attached a TXT file of all of the logs containing "wechsel". |
I've also went through the logs, and filtered for errors and faults I could find was these things
|
I got my hands on a 2015 Macbook that actually runs macOS Monterey. There seems to be a problem with the IOBluetooth Framework on Monterey. Running Because the bluetooth codebase in heavily inspired by blueutil I opened an issue there: |
Folks any update on this? |
@gaurav414u This is still an voluntary-based open source project, please be more polite or help fixing it 🙏🏻 |
Ohh! So sorry for appearing to be rude. |
I released a new version of wechsel that fixes the issue for me. Could you please try out v1.0.2 and verify that the list now gets populated with devices? |
Oooh, thanks, @friedrichweise ! I tried it, but getting an error opening the app: |
As mentioned in the README you have to run |
Closing this now |
I really enjoy using Wechsel, but I'm not sure if it's still maintained.
Under macOS Monterey Wechsel does not work:
The app is starting, but the switcher is not showing, doesn't matter if I select it over the menu bar or trying to launch it via the shortcut.
Edit: It seems that now a window is opening, but without any content (see the attached screenshot). I'm not sure why it started to open now.
The text was updated successfully, but these errors were encountered: