[GH-ISSUE #1855] Accessibility Access fails after updating MacOS Ventura to 3.1 #1355

Closed
opened 2026-05-05 07:45:05 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @ej-github on GitHub (Dec 14, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1855

What happened?

Barrier was working great on Monterey and the GA release of Ventura. I just updated my MBP M1 to Ventura 3.1 and Barrier is stuck on the Accessibility Access screen for System Settings. It is already enabled in there. The only options are to Open System Settings, and Deny.
image
System Settings screenshot:
image

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Downloaded from official release.

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

macOS

What OS versions are you using?

Ventura 3.1

Relevant log output

No response

Any other information

No response

Originally created by @ej-github on GitHub (Dec 14, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1855 ### What happened? Barrier was working great on Monterey and the GA release of Ventura. I just updated my MBP M1 to Ventura 3.1 and Barrier is stuck on the Accessibility Access screen for System Settings. It is already enabled in there. The only options are to Open System Settings, and Deny. ![image](https://user-images.githubusercontent.com/45047655/207625900-ce803b4a-d743-4ec8-8a2b-8efd735f9467.png) System Settings screenshot: ![image](https://user-images.githubusercontent.com/45047655/207626056-7c2f705b-013a-4ca2-89c8-818b7a07f6cc.png) ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Downloaded from official release. ### What OSes are you seeing the problem on? (Check all that apply) macOS ### What OS versions are you using? Ventura 3.1 ### Relevant log output _No response_ ### Any other information _No response_
Author
Owner

@myd-shakepay commented on GitHub (Dec 14, 2022):

Same issue here :(

<!-- gh-comment-id:1351575822 --> @myd-shakepay commented on GitHub (Dec 14, 2022): Same issue here :(
Author
Owner

@myd-shakepay commented on GitHub (Dec 14, 2022):

@ej-github I got it to work by removing it from the accessibility list in system settings and then relaunching barrier + re-enabling.

<!-- gh-comment-id:1351592390 --> @myd-shakepay commented on GitHub (Dec 14, 2022): @ej-github I got it to work by removing it from the accessibility list in system settings and then relaunching barrier + re-enabling.
Author
Owner

@Ligthert commented on GitHub (Dec 14, 2022):

The workaround by @mdewji-shakepay worked for me.

<!-- gh-comment-id:1351613319 --> @Ligthert commented on GitHub (Dec 14, 2022): The workaround by @mdewji-shakepay worked for me.
Author
Owner

@ej-github commented on GitHub (Dec 14, 2022):

@ej-github I got it to work by removing it from the accessibility list in system settings and then relaunching barrier + re-enabling.

Thanks, that worked for me! I was toggling it on/off and didn't see the remove below.

<!-- gh-comment-id:1351680860 --> @ej-github commented on GitHub (Dec 14, 2022): > @ej-github I got it to work by removing it from the accessibility list in system settings and then relaunching barrier + re-enabling. Thanks, that worked for me! I was toggling it on/off and didn't see the remove below.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1355
No description provided.