Would Acorn ever need "Full Disk Access"?

Hi all, I’ve been reviewing the “Full Disk Access” settings on my iMacs and was surprised to see that on my main system I had Acorn in there, but not enabled. Is there any reason why I might have needed to do that? I can’t remember doing it, or why. Does anyone else have Acorn enabled for Full Disk Access?

The only reference that I could find on these forums was this 2022 thread: Suddenly unable to open Acorn files through Applescript or Terminal , where Gus suggests using “Full Disk Access” for Acorn to see if resolves an issue of not being able to open certain files. I haven’t done any scripting with Acorn, which was the context for that thread, so I’m a bit stumped.

Not particularly important, though, if no-one has any comments that is fine. :slightly_smiling_face:

I’m not sure why it would be showing up in that list, and turned off automatically.

I’m the creator of Acorn, and I don’t even have Full Disk Access turned on. But scripting would be a good reason!

Interesting, same here. MacOS 26.2. Was never asked, because had I been, Acorn would definitely been allowed.

r

Just checked the three Macs I have Acorn on, and they all had Acorn listed under Full Disk Access, and it wasn’t enabled on any of them, making me think I was never prompted. Gus mention scripting as a possible culprit - I make heavy use of Keyboard Maestro with Acorn, so that could be the cause in my case.

Thanks folks. So it doesn’t seem like Acorn appearing in my “Full Disk Access” list (not enabled) is unusual. I will assume that it hasn’t happened because of something foolish that I have done, and forgotten about. :blush: