github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1869] Keyboard stoped working on MacOS 13.1 Server #1370

New issue

Open

opened 2026-05-05 07:46:23 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 07:46:23 -06:00

Owner

Originally created by @jkavalec on GitHub (Jan 6, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1869

What happened?

The last Version of MacOS - 13.1 completely breaks Barrier, as it doesn't propagate Keyboard presses to clients. Mouse still works as usual.
When you are on client and perform actions these are still being triggered on the Server (I write this switched by mouse on my Win PC) - Mac, and not on client.
Even switching through keyboard doesn't work at all, you need to physically move mouse to switch.

Information about how did I get here:
First I had Barrier on 2 MacOS 12.x computers, everything worked fine.
I upgraded first to MacOS 13.0.1 - on this version everything worked just fine.
I upgraded second computer a bit later (this time it was 13.1, this version break Barrier completely
At first i tried to verify that no other software interferes.
I verified Mac's Secure Input is not active ioreg -l -w 0 | grep SecureInput
At this point I tried to update second Mac to 13.1, and exactly same problem did appear
I can still use Windows as server and mac as client, but MacOS server just don't work

Part of my debug process with Secure Input was to install ShareMouse software - Barrier alternative, and it worked pretty well, with Mac as Server.

Any ideas for solution?

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

What OSes are you seeing the problem on? (Check all that apply)

macOS

What OS versions are you using?

I am now using
13.1 MacOS on 2 servers
Win 11 Home 22H2 on client (this is 99.9% not relevant, as described above)

Relevant log output

No response

Any other information

No response

Originally created by @jkavalec on GitHub (Jan 6, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1869 ### What happened? The last Version of MacOS - 13.1 completely breaks Barrier, as it doesn't propagate Keyboard presses to clients. Mouse still works as usual. When you are on client and perform actions these are still being triggered on the Server (I write this switched by mouse on my Win PC) - Mac, and not on client. Even switching through keyboard doesn't work at all, you need to physically move mouse to switch. Information about how did I get here: First I had Barrier on 2 MacOS 12.x computers, everything worked fine. I upgraded first to MacOS 13.0.1 - on this version everything worked just fine. I upgraded second computer a bit later (this time it was 13.1, this version break Barrier completely At first i tried to verify that no other software interferes. I verified Mac's Secure Input is not active `ioreg -l -w 0 | grep SecureInput` At this point I tried to update second Mac to 13.1, and exactly same problem did appear I can still use Windows as server and mac as client, but MacOS server just don't work Part of my debug process with Secure Input was to install ShareMouse software - Barrier alternative, and it worked pretty well, with Mac as Server. Any ideas for solution? ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? I am now using 13.1 MacOS on 2 servers Win 11 Home 22H2 on client (this is 99.9% not relevant, as described above) ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:46:26 -06:00

Author

Owner

@markfoodyburton commented on GitHub (Jan 13, 2023):

I have it working ,but if you run the app normally it seems to ask for a permission it already has - endlessly.
I ran it from the terminal (and added the permission to the terminal) - and then 'it worked' - but clearly an issue.

@markfoodyburton commented on GitHub (Jan 13, 2023): I have it working ,but if you run the app normally it seems to ask for a permission it already has - endlessly. I ran it from the terminal (and added the permission to the terminal) - and then 'it worked' - but clearly an issue.

gitea-mirror commented

2026-05-05 07:46:27 -06:00

Author

Owner

@kshashank231 commented on GitHub (Jan 14, 2023):

For the permissions issue, this seems to be more of related to update of MacOS. Found a similar issue here https://www.macworld.com/article/347452/how-to-fix-macos-accessibility-permission-when-an-app-cant-be-enabled.html and the solution works for me!.

So here is what i have done.

Open terminal and sudo tccutil reset Accessibility.
Restart.
Open the app again and grant permission.

@markfoodyburton can you please let us know how your doing this by giving permission using terminal, it might help someday.

Thanks!

@kshashank231 commented on GitHub (Jan 14, 2023): For the permissions issue, this seems to be more of related to update of MacOS. Found a similar issue here https://www.macworld.com/article/347452/how-to-fix-macos-accessibility-permission-when-an-app-cant-be-enabled.html and the solution works for me!. So here is what i have done. 1. Open terminal and `sudo tccutil reset Accessibility`. 2. Restart. 3. Open the app again and grant permission. @markfoodyburton can you please let us know how your doing this by giving permission using terminal, it might help someday. Thanks!

gitea-mirror commented

2026-05-05 07:46:28 -06:00

Author

Owner

@markfoodyburton commented on GitHub (Jan 14, 2023):

added the permission to the terminal then ran the app from the terminal
BUT your suggestions works :-)

@markfoodyburton commented on GitHub (Jan 14, 2023): added the permission to the terminal then ran the app from the terminal BUT your suggestions works :-)

gitea-mirror commented

2026-05-05 07:46:29 -06:00

Author

Owner

@ghost commented on GitHub (Jan 23, 2024):

Having this problem in Mac OS X Sonoma 14.1.2.
Barrier has been added to both "Privacy & Security -> Accessibility" and "Privacy & Security -> Input Monitoring".
Mouse works fine. I can move the mouse to the client, but keyboard input stays on the server 100% and will not go to the client no matter what I try. Never had a problem until today.

Barrier 2.4.0
Mac OS X 14.1.2 (Sonoma)
Client: Void Linux

@ghost commented on GitHub (Jan 23, 2024): Having this problem in Mac OS X Sonoma 14.1.2. Barrier has been added to both "Privacy & Security -> Accessibility" and "Privacy & Security -> Input Monitoring". Mouse works fine. I can move the mouse to the client, but keyboard input stays on the server 100% and will not go to the client no matter what I try. Never had a problem until today. Barrier 2.4.0 Mac OS X 14.1.2 (Sonoma) Client: Void Linux

gitea-mirror commented

2026-05-05 07:46:29 -06:00

Author

Owner

@ghost commented on GitHub (Jan 25, 2024):

Upgrading to MacOS 14.2.1 seems to have fixed the problems. I would try upgrading to the latest MacOSX .. who knows how many bugs lurk in the 13.x codespace as well.

@ghost commented on GitHub (Jan 25, 2024): Upgrading to MacOS 14.2.1 seems to have fixed the problems. I would try upgrading to the latest MacOSX .. who knows how many bugs lurk in the 13.x codespace as well.

gitea-mirror commented

2026-05-05 07:46:30 -06:00

Author

Owner

@hieutoeic23-alt commented on GitHub (Dec 23, 2025):

Hello. Can you help me fix this error? I'm currently using the mouse on both my PC and Mac, but the keyboard only works on the server machine. I've tried everything, but it only shares the mouse, not the keyboard. I'm using an AULA F87 keyboard and a BLE connection to my PC. Please help me

@hieutoeic23-alt commented on GitHub (Dec 23, 2025): Hello. Can you help me fix this error? I'm currently using the mouse on both my PC and Mac, but the keyboard only works on the server machine. I've tried everything, but it only shares the mouse, not the keyboard. I'm using an AULA F87 keyboard and a BLE connection to my PC. Please help me

gitea-mirror commented

2026-05-05 07:46:31 -06:00

Author

Owner

@nbolton commented on GitHub (Dec 23, 2025):

Barrier is no longer in development. Check out Deskflow (upstream) or Input Leap (fork).

https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap

If this is still an issue in those projects, we would appreciate a cross-post of this issue.

@nbolton commented on GitHub (Dec 23, 2025): Barrier is no longer in development. Check out Deskflow (upstream) or Input Leap (fork). https://github.com/deskflow/deskflow https://github.com/input-leap/input-leap If this is still an issue in those projects, we would appreciate a cross-post of this issue.