-
-
Notifications
You must be signed in to change notification settings - Fork 247
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
[BUG] File access popup appears always on macOS 15 Sequoia #1558
Comments
@formattatoio are you still facing this issue? |
I have the same problem after upgrading from macOS 13 to 14 (Sonoma). The only solution for me was to downgrade to V1.1.1 (which I found on my hard disk, fortunately). |
I am using an iMac Pro (Intel) 2017 and Sonoma 14.7.1! |
Thanks for the feedback @Moppel133! Can you reproduce the issue while creating a debug session as stated above? |
Keka_2024-12-11-192254238.log |
Thanks a lot @Moppel133. Can you execute this on the Terminal and let me know the result? xattr -l /Applications/Keka.app > ~/Desktop/keka-xattr.txt After that you can try this other command an see if it fixes the issue: xattr -cr /Applications/Keka.app You can keep two versions of Keka, just rename one of those. |
Thank you for your effort! Here are my results: The "xattr -cr" does not work. I've got (even with sudo); see below. And it did not change the behavior of Keka. [iMac-Pro:~] bluemelk% xattr -cr /Applications/Keka.app |
sudo xattr -cr works if I type it in terminal by myself (before I did copy it from the email). But the behavior of Keka is the same as before! |
Thanks for all the feedback @Moppel133. Closing this one in favor of #1529 that was created previously. |
Some users report the file access popup appearing in bucle, with file access apparently not working.
I'm still unable to reproduce it not once. If you can reproduce this issue, please create a debug session and send the logs here.
Also check out in the
System Settings
-Privacy & Security
-Files & Folders
if you have the offending folders enabled or disabled there:Any additional information can be very helpful so I can reproduce and fix the issue.
The text was updated successfully, but these errors were encountered: