[GH-ISSUE #1322] Barrier stopped working on macOS Catalina; assistive devices does not trust this process #1046

Closed
opened 2026-05-05 07:24:25 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @Realinho on GitHub (Oct 18, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1322

What happened?

Hello all,

Have been using Barrier for several months with no issues whatsoever, other than some difficulties getting some hotkey combinations to work (which I'm positive is related to the OS itself and not Barrier).

As of a few weeks ago, if I remember correctly right after a macOS update, Barrier stopped working. It launches successfully but keeps bouncing on the dock every half-second. Checking the log I notice that it's going through some sort of loop related to privacy settings.
I can confirm that I have added Barrier to the Accessibility and Input Monitoring sections under the Privacy tab of System Settings. Tried removing the entries and re-adding them, to no avail. Is it possible that it's looking for something else?

Version

v2.3.3

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?

Catalina (10.15.7)

Relevant log output

[2021-10-18T12:03:46] FATAL: An error occurred: assistive devices does not trust this process, allow it in system settings.
[2021-10-18T12:03:46] ERROR: process exited with error code: 1
[2021-10-18T12:03:46] INFO: detected process not running, auto restarting

Any other information

No response

Originally created by @Realinho on GitHub (Oct 18, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1322 ### What happened? Hello all, Have been using Barrier for several months with no issues whatsoever, other than some difficulties getting some hotkey combinations to work (which I'm positive is related to the OS itself and not Barrier). As of a few weeks ago, if I remember correctly right after a macOS update, Barrier stopped working. It launches successfully but keeps bouncing on the dock every half-second. Checking the log I notice that it's going through some sort of loop related to privacy settings. I can confirm that I have added Barrier to the Accessibility and Input Monitoring sections under the Privacy tab of System Settings. Tried removing the entries and re-adding them, to no avail. Is it possible that it's looking for something else? ### Version v2.3.3 ### 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? Catalina (10.15.7) ### Relevant log output ```shell [2021-10-18T12:03:46] FATAL: An error occurred: assistive devices does not trust this process, allow it in system settings. [2021-10-18T12:03:46] ERROR: process exited with error code: 1 [2021-10-18T12:03:46] INFO: detected process not running, auto restarting ``` ### Any other information _No response_
gitea-mirror 2026-05-05 07:24:25 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Realinho commented on GitHub (Dec 15, 2021):

This seems to have been fixed with the 2.4.0 version

<!-- gh-comment-id:995093308 --> @Realinho commented on GitHub (Dec 15, 2021): This seems to have been fixed with the 2.4.0 version
Author
Owner

@halfflat commented on GitHub (Jan 4, 2022):

I am getting the same error with v2.4.0 (built from source) under macOS Monterey 12.1. I've confirmed that Barrier has been granted Accessibility permission in the Security&Privacy dialog.

<!-- gh-comment-id:1004483802 --> @halfflat commented on GitHub (Jan 4, 2022): I am getting the same error with v2.4.0 (built from source) under macOS Monterey 12.1. I've confirmed that Barrier has been granted Accessibility permission in the Security&Privacy dialog.
Author
Owner

@halfflat commented on GitHub (Jan 4, 2022):

Update: adding /Applications/Barrier.app/Contents/MacOS/barrier, /Applications/Barrier.app/Contents/MacOS/barrierc, and /Applications/Barrier.app/Contents/MacOS/barriers manually to the permitted applications under Accessibility was sufficient; adding just the application Barrier was insufficient.

<!-- gh-comment-id:1004610320 --> @halfflat commented on GitHub (Jan 4, 2022): Update: adding `/Applications/Barrier.app/Contents/MacOS/barrier`, `/Applications/Barrier.app/Contents/MacOS/barrierc`, and `/Applications/Barrier.app/Contents/MacOS/barriers` manually to the permitted applications under Accessibility was sufficient; adding just the application `Barrier` was insufficient.
Author
Owner

@francotseng commented on GitHub (Oct 10, 2022):

Update: adding /Applications/Barrier.app/Contents/MacOS/barrier, /Applications/Barrier.app/Contents/MacOS/barrierc, and /Applications/Barrier.app/Contents/MacOS/barriers manually to the permitted applications under Accessibility was sufficient; adding just the application Barrier was insufficient.

How to manually add them as allowed applications? Because I can't open the /Applications/Barrier.app/Contents/MacOS directory in the interface

<!-- gh-comment-id:1272826241 --> @francotseng commented on GitHub (Oct 10, 2022): > Update: adding `/Applications/Barrier.app/Contents/MacOS/barrier`, `/Applications/Barrier.app/Contents/MacOS/barrierc`, and `/Applications/Barrier.app/Contents/MacOS/barriers` manually to the permitted applications under Accessibility was sufficient; adding just the application `Barrier` was insufficient. How to manually add them as allowed applications? Because I can't open the `/Applications/Barrier.app/Contents/MacOS` directory in the interface
Author
Owner

@wallneradam commented on GitHub (Jun 28, 2023):

Update: adding /Applications/Barrier.app/Contents/MacOS/barrier, /Applications/Barrier.app/Contents/MacOS/barrierc, and /Applications/Barrier.app/Contents/MacOS/barriers manually to the permitted applications under Accessibility was sufficient; adding just the application Barrier was insufficient.

How to manually add them as allowed applications? Because I can't open the /Applications/Barrier.app/Contents/MacOS directory in the interface

It is an old question, but my answer may help others. Simply frag and frop barrier from /Applications/Barrier.app/Contents/MacOS/barrier . It was enough for me.

<!-- gh-comment-id:1612119159 --> @wallneradam commented on GitHub (Jun 28, 2023): > > Update: adding `/Applications/Barrier.app/Contents/MacOS/barrier`, `/Applications/Barrier.app/Contents/MacOS/barrierc`, and `/Applications/Barrier.app/Contents/MacOS/barriers` manually to the permitted applications under Accessibility was sufficient; adding just the application `Barrier` was insufficient. > > How to manually add them as allowed applications? Because I can't open the `/Applications/Barrier.app/Contents/MacOS` directory in the interface It is an old question, but my answer may help others. Simply frag and frop barrier from `/Applications/Barrier.app/Contents/MacOS/barrier` . It was enough for me.
Author
Owner

@facundopadilla commented on GitHub (Nov 21, 2024):

Hello! I had the same issue. With InputLeap, I can't connect my other desktop to my MacBook, so:

  1. Drag and drop the Barrier app to the desktop.
  2. Allow accessibility permissions.
  3. Create the SSL certificate, check it here: https://github.com/debauchee/barrier/issues/1609#issuecomment-1066938159.
  4. On your server (Mac), configure it by adding a new device (make sure the client device added to your Mac has the same name).
  5. On your client (in my case, Windows), enable SSL connection in Barrier -> Change Settings -> Enable SSL, click the OK button, and activate the "Auto config" checkbox.
  6. Enjoy!
<!-- gh-comment-id:2491459541 --> @facundopadilla commented on GitHub (Nov 21, 2024): Hello! I had the same issue. With InputLeap, I can't connect my other desktop to my MacBook, so: 1. Drag and drop the Barrier app to the desktop. 2. Allow accessibility permissions. 3. Create the SSL certificate, check it here: https://github.com/debauchee/barrier/issues/1609#issuecomment-1066938159. 4. On your server (Mac), configure it by adding a new device (make sure the client device added to your Mac has the same name). 5. On your client (in my case, Windows), enable SSL connection in Barrier -> Change Settings -> Enable SSL, click the OK button, and activate the "Auto config" checkbox. 6. Enjoy!
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#1046
No description provided.