macOS Sequoia (15.5..0) and permissions

Paul Dupuis paul at researchware.com
Thu Jun 5 13:36:24 EDT 2025


I know most macOS users have full admin of their computers, but in some 
of our users are students on university lab systems where permissions 
are restricted.

I have run into a problem where 'the detailed folders' is failing with 
an execution error "get: error in expression: (Line 2695, column 9)"
thePath is the path to a folder, including the folder. For example: 
/Users/Paul/Documents/My Research/Study123/Sources
'Sources' is a folder.
The pathTo function return the path to that folder, example: 
/Users/Paul/Documents/My Research/Study123

The problem code snippet is:

set the defaultFolder to pathTo(thePath) -- so in this example, 
defaultFolder is set to /Users/Paul/Documents/My Research/Study123
if there is a folder thePath then -- As there is a folder 
/Users/Paul/Documents/My Research/Study123/Sources, this is true
   get the detailed folders -- line 2695 error!
end if

The 'get the detailed folders' should have returned to me the detailed 
information for the folder 'Sources" (assuming that is the only folder 
in the Study123 folder)

This works where the user has full permissions
This has worked in the past where the has not had write permission to 
the target folder
This blew up under 15.5.0 (latest Sequoia update). Neither I, nor the 
poor student, know what the permissions were or how to find out. They 
may not even have access to the same computer the next time they use the 
lab. Of course, I could assume all lab computers are configured the 
same. However, the student is udner a deadline (like many student) and 
probably does not have time to troubleshoot this further as saving to a 
different location worked.

I can always enclose the 'get detailed folders' in a try...end try and 
trap the error, but I am wondering is anyone know what is going on? This 
is under LC 9.6.13 standalone.

If they don't have permission, I just want to warn them, so I can do it 
with a try..end try, but this all has me curious if Apple ever further 
sand boxing just broke another LC feature.


More information about the use-livecode mailing list