[GH-ISSUE #562] Accessibility issue on MacOS 15.1 when using the extension #376

Open
opened 2026-03-03 01:12:03 +03:00 by kerem · 5 comments
Owner

Originally created by @edumesnil on GitHub (Nov 8, 2024).
Original GitHub issue: https://github.com/Clipy/Clipy/issues/562

Hi there -- First, love the extension!

However, I am unsure if it's since upgrading to 15 or 15.1, but I'm always getting prompted to allow access in settings when using the extension now, even though it is enabled:

image
image

The extension is up to date. Any idea what's up? Is anyone else having this issue?

Thanks!

Originally created by @edumesnil on GitHub (Nov 8, 2024). Original GitHub issue: https://github.com/Clipy/Clipy/issues/562 Hi there -- First, love the extension! However, I am unsure if it's since upgrading to 15 or 15.1, but I'm always getting prompted to allow access in settings when using the extension now, even though it is enabled: ![image](https://github.com/user-attachments/assets/448aecc5-748e-4176-a19e-a81f54d1ca65) ![image](https://github.com/user-attachments/assets/433fe225-5d8c-405b-af85-dae61b8d7c4a) The extension is up to date. Any idea what's up? Is anyone else having this issue? Thanks!
Author
Owner

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

I'm getting the same error :(

<!-- gh-comment-id:2490368094 --> @grifosh commented on GitHub (Nov 21, 2024): I'm getting the same error :(
Author
Owner

@tkmud commented on GitHub (Nov 23, 2024):

Me too. Same error....

<!-- gh-comment-id:2495389903 --> @tkmud commented on GitHub (Nov 23, 2024): Me too. Same error....
Author
Owner

@edumesnil commented on GitHub (Nov 26, 2024):

Update : I updated this weekend to 15.1.1 and the issue seems to be resolved.

<!-- gh-comment-id:2501798446 --> @edumesnil commented on GitHub (Nov 26, 2024): Update : I updated this weekend to 15.1.1 and the issue seems to be resolved.
Author
Owner

@kirtom commented on GitHub (Dec 1, 2024):

After macOS 15 upgrade, it felt just different: something had changed, and something important was gone. Deep down, I sensed an unsettling, nagging feeling that something was missing. I couldn’t pinpoint it at first, but with every text I edited, every email I sent, and every comment I made, the void grew larger, like a gaping abyss in my soul.

Then, it hit me like a bolt of lightning: CLIPY IS NOT WORKING!

<!-- gh-comment-id:2509800442 --> @kirtom commented on GitHub (Dec 1, 2024): After macOS 15 upgrade, it felt just different: something had changed, and something important was gone. Deep down, I sensed an unsettling, nagging feeling that something was missing. I couldn’t pinpoint it at first, but with every text I edited, every email I sent, and every comment I made, the void grew larger, like a gaping abyss in my soul. Then, it hit me like a bolt of lightning: CLIPY IS NOT WORKING!
Author
Owner

@tkmud commented on GitHub (Dec 3, 2024):

I have updated 15.1.1, but I still got the same error...

<!-- gh-comment-id:2514369438 --> @tkmud commented on GitHub (Dec 3, 2024): I have updated 15.1.1, but I still got the same error...
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
starred/Clipy#376
No description provided.