github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #169] App keeps on asking Accessibility access every start even if it already allowed. #124

New issue

Closed

opened 2026-05-05 05:06:40 -06:00 by gitea-mirror · 13 comments

gitea-mirror commented

2026-05-05 05:06:40 -06:00

Owner

Originally created by @willerbee on GitHub (Jan 9, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/169

Same goes for other forks, it always ask for accessibility, except for JonyVR's 1.3.1 (the only one that doesn't seem to ask after allowing)

OS: Mojave 10.14.6

Originally created by @willerbee on GitHub (Jan 9, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/169 ![ss1](https://user-images.githubusercontent.com/10969215/72061358-ab9e6800-3310-11ea-97a2-9fc7181385dd.jpg) ![ss2](https://user-images.githubusercontent.com/10969215/72061343-a3dec380-3310-11ea-8c49-d014a58d943b.jpg) Same goes for other forks, it always ask for accessibility, except for JonyVR's 1.3.1 (the only one that doesn't seem to ask after allowing) OS: Mojave 10.14.6

gitea-mirror

2026-05-05 05:06:40 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:06:47 -06:00

Author

Owner

@JoniVR commented on GitHub (Jan 9, 2020):

Have you tried removing it from the list and then adding it again?

@JoniVR commented on GitHub (Jan 9, 2020): Have you tried removing it from the list and then adding it again?

gitea-mirror commented

2026-05-05 05:06:51 -06:00

Author

Owner

@willerbee commented on GitHub (Jan 9, 2020):

Yep, did that. I also tried removing it, closing the app, adding the app by dragging the app to the list (and also another round using + button) before I started the app. It's as if the app doesn't know that it has already been allowed. Your 1.3.1 seems to have no problems.

@willerbee commented on GitHub (Jan 9, 2020): Yep, did that. I also tried removing it, closing the app, adding the app by dragging the app to the list (and also another round using + button) before I started the app. It's as if the app doesn't know that it has already been allowed. Your 1.3.1 seems to have no problems.

gitea-mirror commented

2026-05-05 05:06:54 -06:00

Author

Owner

@JoniVR commented on GitHub (Jan 9, 2020):

Can you test if the hotkeys actually work regardless? If they do then it's probably a bug with the dialog itself.

@JoniVR commented on GitHub (Jan 9, 2020): Can you test if the hotkeys actually work regardless? If they do then it's probably a bug with the dialog itself.

gitea-mirror commented

2026-05-05 05:06:57 -06:00

Author

Owner

@willerbee commented on GitHub (Jan 9, 2020):

Nope, hotkeys doesn't work. (but in your 1.3.1 it does)

@willerbee commented on GitHub (Jan 9, 2020): Nope, hotkeys doesn't work. (but in your 1.3.1 it does)

gitea-mirror commented

2026-05-05 05:06:59 -06:00

Author

Owner

@JoniVR commented on GitHub (Jan 9, 2020):

Seems to be happening on Catalina too for some people. Will have to look into it in the future.

@JoniVR commented on GitHub (Jan 9, 2020): Seems to be happening on Catalina too for some people. Will have to look into it in the future.

gitea-mirror commented

2026-05-05 05:07:05 -06:00

Author

Owner

@willerbee commented on GitHub (Jan 9, 2020):

God bless you

@willerbee commented on GitHub (Jan 9, 2020): God bless you

gitea-mirror commented

2026-05-05 05:07:07 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 21, 2020):

Hi, is this still an issue?

@JoniVR commented on GitHub (Jun 21, 2020): Hi, is this still an issue?

gitea-mirror commented

2026-05-05 05:07:09 -06:00

Author

Owner

@willerbee commented on GitHub (Jun 21, 2020):

Hi Joni, no this is fixed <3 thank you

@willerbee commented on GitHub (Jun 21, 2020): Hi Joni, no this is fixed <3 thank you

gitea-mirror commented

2026-05-05 05:07:11 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 21, 2020):

Glad to hear! 🙂

@JoniVR commented on GitHub (Jun 21, 2020): Glad to hear! 🙂

gitea-mirror commented

2026-05-05 05:07:14 -06:00

Author

Owner

@MahatmaFatalError commented on GitHub (Jan 28, 2022):

This issue re-appears with macOS 12.2 and MonitorControl 4.0.2

@MahatmaFatalError commented on GitHub (Jan 28, 2022): This issue re-appears with macOS 12.2 and MonitorControl 4.0.2

gitea-mirror commented

2026-05-05 05:07:16 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 28, 2022):

Hi, this is a known macOS bug. Drag the MonitorControl app from the Applications folder into the list of approved apps even if MonitorControl is already listed there, that should fix it.

@waydabber commented on GitHub (Jan 28, 2022): Hi, this is a known macOS bug. Drag the MonitorControl app from the Applications folder into the list of approved apps even if MonitorControl is already listed there, that should fix it.

gitea-mirror commented

2026-05-05 05:07:17 -06:00

Author

Owner

@MahatmaFatalError commented on GitHub (Jan 28, 2022):

Hi, this is a known macOS bug.

Is there already a radar https://openradar.appspot.com/ filed?

Drag the MonitorControl app from the Applications folder into the list of approved apps even if MonitorControl is already listed there, that should fix it.

Thx, will try.

@MahatmaFatalError commented on GitHub (Jan 28, 2022): > Hi, this is a known macOS bug. Is there already a radar https://openradar.appspot.com/ filed? > Drag the MonitorControl app from the Applications folder into the list of approved apps even if MonitorControl is already listed there, that should fix it. Thx, will try.

gitea-mirror commented

2026-05-05 05:07:20 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 28, 2022):

I don't know. It's been like this since the feature appeared in macOS. :)

@waydabber commented on GitHub (Jan 28, 2022): I don't know. It's been like this since the feature appeared in macOS. :)