Bug: some folders and sub items will not displayed

[Fischmuetze]

macOS Sonoma 14.5
MacBook Pro 14", M1

App Version 1.5.9 (32)

Folder and Pictures in ~/Library/Messages and subdirectories will not displayed / will ignored.
Picture Browsers like XnView MP have no problems with this folder

[gobbledegook]

This is due to your System Settings configuration. You need to allow "Full Disk Access" per application, or enable specific folders under Privacy & Security.

[Fischmuetze]

ok I see. I wonder why there is no message like other apps trigger Anyway thanksSteffenAm 05.06.2024 um 20:07 schrieb Dominic Yu ***@***.***>: This is due to your System Settings configuration. You need to allow "Full Disk Access" per application, or enable specific folders under Privacy & Security. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[DJFriar]

I imagine there is no message because that particular use is not common for this app. The Full Disk Access message is rather scary to an average user, and requires a bunch of steps that the average user isn't familiar with; just like most users have no idea that ~/Library even exists since it requires additional knowledge to even access it.

If I was the dev I also wouldn't have programmed in any alert for this and just assumed if you know enough to get to those locations and why you would; that you would know about the Full Disk Access requirement and that you would need to enable it. This app isn't a power tool for computer geeks; if it is aimed at any geek it would be photography geeks at most.

*Full disclosure, I am not the dev and not involved in the development of this app in any shape or form whatsoever; I'm just sharing my $0.02 on why the dialogs were likely not included.

[Fischmuetze]

For the most parts of your post I agree but if an app cant access a folder by missing permissions it should show a message. That message should fair enough for giving a hint to solving the situation. Am 05.06.2024 um 21:45 schrieb Tommy Craft ***@***.***>: I imagine there is no message because that particular use is not common for this app. The Full Disk Access message is rather scary to an average user, and requires a bunch of steps that the average user isn't familiar with; just like most users have no idea that ~/Library even exists since it requires additional knowledge to even access it. If I was the dev I also wouldn't have programmed in any alert for this and just assumed if you know enough to get to those locations and why you would; that you would know about the Full Disk Access requirement and that you would need to enable it. This app isn't a power tool for computer geeks; if it is aimed at any geek it would be photography geeks at most. *Full disclosure, I am not the dev and not involved in the development of this app in any shape or form whatsoever; I'm just sharing my $0.02 on why the dialogs were likely not included. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[gobbledegook]

Apple has been changing file access permissions (specifically, making everything more strict) with each new release of macOS. Apple views third-party application access to "weird" directories to be completely the responsibility of the user, not the app developer. I don't think it's even possible to bring up a "Full Disk Access" dialog in the latest macOS.

Also wanted to point out that "missing permissions" is different from file access privileges granted to apps. If you try to navigate to /Users/someotheruser/Desktop you'll see a little "Do not enter" (red circle with white horizontal bar icon) on the folder to indicate that the permissions prevent you from seeing the contents of the directory. This is different from trying to access special folders that you (the user) do have permissions for, but the os isn't bestowing access privileges to the current process (Phoenix Slides). I'm not sure if there's a way to detect this programmatically.