Page 1 of 1

Disk Access Permissions for the Debugger

Posted: Mon Feb 19, 2024 11:06 pm
by DannyWeijermans
I'm not 100% sure that it's a bug,
but when using the latest 6.10 beta 4 version of PureBasic in Sonoma 14.3.1 (latest)
the debugger doesn't ask for Full Disk Access (or specific Files and Folders access
when run.
I noticed this behaviour when using AppleScript in PureBasic
to obtain the 'root disk-name' (no other way I think..)
After creating the executable,
the executable DOES ask for these permissions..
Any thought on this?
Many thanks to Shardik for helping me solve this puzzle..
Regards,
Danny Weijermans - The Netherlands

Re: Disk Access Permissions for the Debugger

Posted: Thu Feb 22, 2024 2:32 pm
by Fred
I have no idea, it should be prompted automatically I guess.

Re: Disk Access Permissions for the Debugger

Posted: Thu Feb 22, 2024 5:29 pm
by DannyWeijermans
Hi Fred!
That's the strange thing:
it doesn't prompt automatically
when using the Debugger..

Re: Disk Access Permissions for the Debugger

Posted: Thu Feb 22, 2024 8:51 pm
by mk-soft
Take a look at macOS privacy and security.
In my case, the PureBasic IDE has folder permissions on different folders.
When the code is started under PureBasic with debugger, it has the same permissions as the PureBasic IDE. So the permission is inherited.
As Executable App the permission must be granted first.

Re: Disk Access Permissions for the Debugger

Posted: Thu Feb 22, 2024 9:17 pm
by DannyWeijermans
Aha! I think I know where the problem was:
I also still had PureBasic 5.73 in my apps,
and it was 'overruling' the disk permissions macOS privacy and security.
Isn't it possible to have both apps in Sonoma?
I noticed that files kept opening in 5.73,
even if I set it in file-info to open in PureBasic 6.10 beta 4..
I now removed the old PB,
and macOS privacy and security
allows me to give Full Disk Access to PB6..

Re: Disk Access Permissions for the Debugger

Posted: Thu Feb 22, 2024 10:21 pm
by mk-soft
I also have many versions of PureBasic in different subfolders. The problem is all have the same APP name and so the files are always started with the first found IDE (so the oldest).
I have not found a solution either, except to rename the PureBasic.app to PureBasic-vXXX.app.