mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1860] macOS Ventura 13.1 FATAL: An error occurred: assistive devices does not trust this process, allow it in system settings. #1361
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1361
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @antigraviton on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1860
What happened?
barrier.app but also barriers exit with the fatal error mentioned above, despite being authorised under System Settings / Privacy & Security / Accessibility.
For good measure, I authorised all the underlying executables:
/Applications/Barrier.app/Contents/MacOS/*
macOS Ventura 13.1
barrier 2.4.0
Barrier stopped working completely except from a terminal since the latest macOS release, a few days ago.
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
GitHub (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?
macOS Ventura 13.1
Relevant log output
Any other information
No response
@AWHubGit commented on GitHub (Dec 17, 2022):
macOS 13.1 Ventura with Barrier.app vers 2.4.0
Launching barrier.app or CLI "open -a barrier" each time dialog appears asking to allow barrier to control assistance.
Barrier has been added under System Settings / Privacy & Security / Accessibility, but despite this each time dialog is coming.
It's not possible to use/launch Barrier anymore under macOS 13.1.
Before 13.1 no problems.
@antigraviton commented on GitHub (Dec 17, 2022):
I can still start it in a terminal:
% /Applications/Barrier.app/Contents/MacOS/barriers -c /etc/barrier.conf --address xxx -name xxx <more options here>@mzupan commented on GitHub (Dec 17, 2022):
dead for me too. I can't even start it from a terminal.
Nothing starts
@gogoizzy commented on GitHub (Dec 19, 2022):
I cannot open it either. Cannot find *.conf on my mac either so cannot open in terminal. Added all three executables barrier, barriers and barrierc as per user suggestion in Issue 1322 but still getting same error.
@TamilNeram commented on GitHub (Dec 19, 2022):
same here. waiting for the fix...
@SangNguyenTL commented on GitHub (Dec 19, 2022):
I also got the same error
@cigumo commented on GitHub (Dec 19, 2022):
+1
@cigumo commented on GitHub (Dec 19, 2022):
I solved it by removing both barrier entries (Privacy & Security > Accessibility and Privacy & Security > Input Monitoring), restaring barrier and manually adding the one in Accessibility.
@SangNguyenTL commented on GitHub (Dec 19, 2022):
It's worked. Tks.
@roughwood commented on GitHub (Dec 19, 2022):
This solved it for me as well. I'll list the steps I took just in case anyone else was confused:
@gogoizzy commented on GitHub (Dec 20, 2022):
Concur the above solution works :)
@robywoo commented on GitHub (Dec 29, 2022):
Did above but there is no prompt for Accessibility option Just the same malware warning- not sure this solution is for Ventura as the system settings panel has a different layout than what is described
@robywoo commented on GitHub (Dec 29, 2022):
Just discovered that in the Privacy & Security settings you have to scroll down to Security and allow anyway for Barrier
@owidat commented on GitHub (Jan 22, 2023):
Please note that for macOS Ventura 13.1 + you need to go for Privacy & Security > Accessibility and Privacy & Security > App Management , then click on the + and select barrier App
Also you need to do steps in the following comment (https://github.com/debauchee/barrier/issues/1860#issuecomment-1358566360)
@moshen commented on GitHub (Jan 27, 2023):
Barrier was in the list, I removed it, re-added it and it started working for me.
@Clailton commented on GitHub (Feb 22, 2023):
Thanks for solution. It's Worked perfect for me.
@Candorada2 commented on GitHub (Mar 3, 2023):
if nothing works. then try this
(Privacy & Security > Accessibility and Privacy & Security > Input Monitoring) - Add Barrier Into Here.
remove barrier from both the Accesability and Input monitoring registaries.
open barrier. and enable it. then it should work after launching it
@Anatoly03 commented on GitHub (Dec 11, 2023):
For me, barrier works, but I can't run it over console, I tried the above, any ideas?
@xerxesb commented on GitHub (Nov 16, 2024):
If anyone like me was Googling connectivity issues with InputLeap (aka fork of Barrier), and macOS Sonoma (or later), I was getting the same error in the log:
and the steps above to include the .app in the Accessibility permissions wasn't enough.
I had to open the
inputleap.apppackage contents and also grant/allow the binaries underContents/MacOS/under Privacy -> AccessibilityThat did the trick.
@hiarmen commented on GitHub (Nov 16, 2024):
Bless you, bearded man!!!
@bitskc commented on GitHub (Nov 17, 2024):
This worked, thank you! If anyone else like me was trying to figure out how to do this, you go to Finder, right click InputLeap.app --> Show Package Contents. Then go to Settings --> Privacy --> Accessibility and drag the binaries from the Finder window over to the settings and it'll add them. I was struggling, trying to do it via the + button and that wasn't working...
@EVINK commented on GitHub (Nov 26, 2024):
Works for Deskflow, too !
@KinglyWayne commented on GitHub (Nov 27, 2024):
Thank you. This worked for me
@GenhaoLi commented on GitHub (Dec 27, 2024):
Thanks for the detailed steps. In case anyone wanna make the approved list in
Settings | Privacy & Security | Accessibilitymore manageable, only these 3 executable files are required:@BKR-dev commented on GitHub (Aug 27, 2025):
On a Macbook M2 this is the trick if you use the Apple_Silicon binary
"I had to open the inputleap.app package contents and also grant/allow the binaries under Contents/MacOS/ under Privacy -> Accessibility"
You open the "App" right click Show Content and then execute the input-leap executable and allow its permissions. Weirdly for me, i need to then always execute this exact executable to get the server starting, the App Package does not work.
But hey, as long as it works :)
@nbolton commented on GitHub (Aug 27, 2025):
Try Deskflow or Input Leap, as Barrier is no longer in development.
https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap
The 'Insights' tab of each GitHub project may help you decide which one to use.
Both are compatible with Barrier client/server, so you can try on one of your computers.
If this is still an issue in those projects, we would appreciate a cross-post of this issue.