github-starred/barrier

Fork 0

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

[GH-ISSUE #1736] Accessibility Access Stops Barrier from Launching on MacOs Client after Monterey 12.5 Update #1283

New issue

Open

opened 2026-05-05 07:41:39 -06:00 by gitea-mirror · 12 comments

gitea-mirror commented

2026-05-05 07:41:39 -06:00

Owner

Originally created by @benrifkah on GitHub (Aug 4, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1736

What happened?

Actual Result
After installing the Monterey 12.5 update, the OS blocks Barrier from launching and prompts the user to give it permission to control the computer even though the permission was already granted and the OS was previously allowing Barrier to launch and control the computer.

Expected Result
After an OS update MacOS sees that Barrier already has permission to control the computer and launches the application without prompting the user to give it permission.

Details
My client has been working for months and Barrier was already granted permission to control the computer via accessibility controls. After installing the Monterey 12.5 update, attempts to start Barrier on the MacOs client trigger an "Accessibility Access" dialog with the following message:

"Barrier" would like to control this computer using
accessibility features.
Grant access to this application in Security & Privacy
preferences, located in System Preferences.
[Open System Preferences] [Deny]

Clicking the "[Open System Preferences]" button opens the Accessibility permissions list in the System Preferences Privacy pane. Barrier is already listed as an accessibility app and it is already checked as having the computer control permission. Barrier does not launch after opening the preferences pane and making changes nor after clicking deny.

Even unchecking and re-checking the box for the Barrier permission didn't resolve the issue.

Nothing else on my Mac changed besides the OS update so it looks to me like Barrier somehow lost its association with its previously granted permission after the 12.5 update.

I would expect Barrier to remain associated with its previously granted permission after an OS update.

I was able to get barrier to run by:

revoking the permission
removing Barrier from the list of accessibility apps
restarting my Mac
re-granting the permission.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

https://github.com/debauchee/barrier/releases/download/v2.4.0/Barrier-2.4.0-release.dmg

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

macOS

What OS versions are you using?

Client: MacOs Monterey 12.5
Server: Windows 10 Version 21H2 (OS Build 19044.1826)

Relevant log output

The client log doesn't show anything from before I reinstalled and was able to start Barrier.

Any other information

No response

Originally created by @benrifkah on GitHub (Aug 4, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1736 ### What happened? **Actual Result** After installing the Monterey 12.5 update, the OS blocks Barrier from launching and prompts the user to give it permission to control the computer even though the permission was already granted and the OS was previously allowing Barrier to launch and control the computer. **Expected Result** After an OS update MacOS sees that Barrier already has permission to control the computer and launches the application without prompting the user to give it permission. **Details** My client has been working for months and Barrier was already granted permission to control the computer via accessibility controls. After installing the Monterey 12.5 update, attempts to start Barrier on the MacOs client trigger an "Accessibility Access" dialog with the following message: ![Screen Shot 2022-08-04 at 10 42 15 AM](https://user-images.githubusercontent.com/94815/182956316-0775a9eb-7dd0-4d5b-966b-89c8d54587dc.png) > "Barrier" would like to control this computer using > accessibility features. > Grant access to this application in Security & Privacy > preferences, located in System Preferences. > [Open System Preferences] [Deny] Clicking the "[Open System Preferences]" button opens the Accessibility permissions list in the System Preferences Privacy pane. Barrier is already listed as an accessibility app and it is already checked as having the computer control permission. Barrier does not launch after opening the preferences pane and making changes nor after clicking deny. Even unchecking and re-checking the box for the Barrier permission didn't resolve the issue. Nothing else on my Mac changed besides the OS update so it looks to me like Barrier somehow lost its association with its previously granted permission after the 12.5 update. I would expect Barrier to remain associated with its previously granted permission after an OS update. **I was able to get barrier to run by:** 1. revoking the permission 2. removing Barrier from the list of accessibility apps 3. restarting my Mac 4. re-granting the permission. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? https://github.com/debauchee/barrier/releases/download/v2.4.0/Barrier-2.4.0-release.dmg ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? Client: MacOs Monterey 12.5 Server: Windows 10 Version 21H2 (OS Build 19044.1826) ### Relevant log output ```shell The client log doesn't show anything from before I reinstalled and was able to start Barrier. ``` ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:41:42 -06:00

Author

Owner

@acaldas1984 commented on GitHub (Aug 22, 2022):

Please, the workaround doesn't work for me. I'm on Mac Monterey 12.3 on a M1 pro. Previous barrier version was not working well and I had to install latest. Any help?

@acaldas1984 commented on GitHub (Aug 22, 2022): Please, the workaround doesn't work for me. I'm on Mac Monterey 12.3 on a M1 pro. Previous barrier version was not working well and I had to install latest. Any help?

gitea-mirror commented

2026-05-05 07:41:44 -06:00

Author

Owner

@albertcaldas84 commented on GitHub (Aug 22, 2022):

Compiling the source code doesn't help, I have the same issue.

@albertcaldas84 commented on GitHub (Aug 22, 2022): Compiling the source code doesn't help, I have the same issue.

gitea-mirror commented

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

Author

Owner

@sandeep-khanna commented on GitHub (Aug 25, 2022):

Same issue here. Are there any reliable and successful workarounds?

@sandeep-khanna commented on GitHub (Aug 25, 2022): Same issue here. Are there any reliable and successful workarounds?

gitea-mirror commented

2026-05-05 07:41:47 -06:00

Author

Owner

@skinlayers commented on GitHub (Sep 17, 2022):

I was able to fix this issue by running:
sudo tccutil reset Accessibility
And then immediately rebooting.

See How to fix macOS Accessibility permission when an app can’t be enabled

@skinlayers commented on GitHub (Sep 17, 2022): I was able to fix this issue by running: `sudo tccutil reset Accessibility` And then immediately rebooting. See [How to fix macOS Accessibility permission when an app can’t be enabled ](https://www.macworld.com/article/347452/how-to-fix-macos-accessibility-permission-when-an-app-cant-be-enabled.html)

gitea-mirror commented

2026-05-05 07:41:47 -06:00

Author

Owner

@robywoo commented on GitHub (Dec 29, 2022):

Having similar issues with MACOS Ventura 13. Have allowed Barrier app in privacy settings. But I still get the malware warning. Do I need to reboot?

@robywoo commented on GitHub (Dec 29, 2022): Having similar issues with MACOS Ventura 13. Have allowed Barrier app in privacy settings. But I still get the malware warning. Do I need to reboot?

gitea-mirror commented

2026-05-05 07:41:48 -06:00

Author

Owner

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

I found a solution:

In the Accessibility control panel, remove Barrier from the list using the Minus button below it.

Re-open and re-approve it.

Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed.

@neolefty commented on GitHub (Jan 13, 2023): I found a solution: 1. In the **Accessibility** control panel, remove **Barrier** from the list using the **Minus** button below it. <img width="206" alt="image" src="https://user-images.githubusercontent.com/242916/212417618-9a53ac37-a0a3-45ae-a2a6-4d3b8e60a17c.png"> 2. Re-open and re-approve it. Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed.

gitea-mirror commented

2026-05-05 07:41:49 -06:00

Author

Owner

@lwmcal commented on GitHub (Feb 10, 2023):

I found a solution:

In the Accessibility control panel, remove Barrier from the list using the Minus button below it.

Re-open and re-approve it.

Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed.

This workaround works perfectly for me. I am using Barrier 2.40 and Ventura 13.2

@lwmcal commented on GitHub (Feb 10, 2023): > I found a solution: > > 1. In the **Accessibility** control panel, remove **Barrier** from the list using the **Minus** button below it. > > <img alt="image" width="206" src="https://user-images.githubusercontent.com/242916/212417618-9a53ac37-a0a3-45ae-a2a6-4d3b8e60a17c.png"> > > 2. Re-open and re-approve it. > > Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed. This workaround works perfectly for me. I am using Barrier 2.40 and Ventura 13.2

gitea-mirror commented

2026-05-05 07:41:50 -06:00

Author

Owner

@gabrielmisa commented on GitHub (Feb 22, 2023):

It did work for me. I was doing something similar (Uninstalling, rebooting and installing), but, It's was not the same; The step REMOVE the permissions, rebooting and re-installing worked perfectly.

Captura de pantalla 2023-02-22 a la(s) 08 51 43

@gabrielmisa commented on GitHub (Feb 22, 2023): It did work for me. I was doing something similar (Uninstalling, rebooting and installing), but, It's was not the same; The step REMOVE the permissions, rebooting and re-installing worked perfectly. <img width="818" alt="Captura de pantalla 2023-02-22 a la(s) 08 51 43" src="https://user-images.githubusercontent.com/23196581/220612609-f4725f00-ac4e-4762-98ab-430f1d7ad8d2.png">

gitea-mirror commented

2026-05-05 07:41:50 -06:00

Author

Owner

@derekvantonder commented on GitHub (Mar 19, 2023):

I had this issue too, stopping me from using Barrier. I think this issue is going to be so common as people upgrade to macOS Venture that it's worth putting a big note about it in the README.md. I was able to fix it using the instructions above, but man I nearly uninstalled Barrier and paid for Share Mouse. Amazing piece of software BTW.

@derekvantonder commented on GitHub (Mar 19, 2023): I had this issue too, stopping me from using Barrier. I think this issue is going to be so common as people upgrade to macOS Venture that it's worth putting a big note about it in the README.md. I was able to fix it using the instructions above, but man I nearly uninstalled Barrier and paid for Share Mouse. Amazing piece of software BTW.

gitea-mirror commented

2026-05-05 07:41:51 -06:00

Author

Owner

@TylerThompson commented on GitHub (May 21, 2023):

I was able to fix this issue by running:
sudo tccutil reset Accessibility
And then immediately rebooting.

This worked for me! Believe this is the same thing as what everyone is mentioning with the UI Portions

@TylerThompson commented on GitHub (May 21, 2023): > I was able to fix this issue by running: > sudo tccutil reset Accessibility > And then immediately rebooting. This worked for me! Believe this is the same thing as what everyone is mentioning with the UI Portions

gitea-mirror commented

2026-05-05 07:41:53 -06:00

Author

Owner

@markian-rybchuk commented on GitHub (Jul 17, 2023):

sudo tccutil reset Accessibility

this worked for me :)

@markian-rybchuk commented on GitHub (Jul 17, 2023): > `sudo tccutil reset Accessibility` this worked for me :)

gitea-mirror commented

2026-05-05 07:41:54 -06:00

Author

Owner

@glenpereira commented on GitHub (Nov 25, 2023):

I found a solution:
1. In the **Accessibility** control panel, remove **Barrier** from the list using the **Minus** button below it.
2. Re-open and re-approve it.
Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed.

Thanks! This worked for me. I am using Barrier 2.4.0 and Ventura 13.6

@glenpereira commented on GitHub (Nov 25, 2023): > I found a solution: > > 1. In the **Accessibility** control panel, remove **Barrier** from the list using the **Minus** button below it. > > > <img alt="image" width="206" src="https://user-images.githubusercontent.com/242916/212417618-9a53ac37-a0a3-45ae-a2a6-4d3b8e60a17c.png"> > > 2. Re-open and re-approve it. > > > Probably the same effect as @skinlayers but less disruptive (doesn't reset other applications), and no CLI needed. Thanks! This worked for me. I am using Barrier 2.4.0 and Ventura 13.6

No labels

Rows
Columns