Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS 13.1 (22C65) prevents Barrier from running due to permissions issue? #1856

Closed
TheDreamsWind opened this issue Dec 15, 2022 · 2 comments

Comments

@TheDreamsWind
Copy link

What happened?

After recent update it seems like macOS doesn't allow Barrier to run. Upon launching the system shows a dialog saying that the app would like to control this computer:

Screenshot 2022-12-15 at 9 43 36 AM

However if you open the privacy & security settings all permissions are already given.

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?

macOS Ventura 13.1 (22C65)

Relevant log output

No response

Any other information

No response

@TheDreamsWind
Copy link
Author

Sorry for rushing with the issue. It seems like the previous permission became obsolete for some reason, so I had to remove the Barrier app from the Privacy & Security / Accessibility menu (via the minus button under the list), and after relaunching Barrier again, was able to successfully give the required permission:

Screenshot 2022-12-15 at 9 50 28 AM

@TheDreamsWind TheDreamsWind changed the title macOS 13.1 (22C65) prevents Barrier from running? macOS 13.1 (22C65) prevents Barrier from running due to permissions issue? Dec 15, 2022
@ForbiddenEra
Copy link

This worked for me but not first try; even the second try I had to actually click "Open System Settings" in that window even though it was already open and enabled. Was worried that it was pure fkd after MacOS 14 update, I need this software and sucks it's unmaintained and the new fork of this already forked version is not quite ready apparently.. ugh

Weird how this has been forked so many times and there's not (m)any good open source solutions for this and even commercial ones aren't that great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants