Posts

Post not yet marked as solved
8 Replies
Hello Eskimo, Thanks for responding.As you suspected, the configuration is more complicated than I implied in my first post - perhaps I oversimplified.The "failing" process is a tty application (called "dyalog") that can run in a number of ways, including as an interactive session in a tty/Terminal window, or as a TCPIP server, communicating with a parent GUI Application (called "Dyalog 18.0")When running interactively inside Termimal, and "dyalog" calls opendir, Terminal pops up with "Teminal eould like to access files in your Documents folder"). I can click "OK" and the call succeeds.The GUI application (Dyalog 18.0) is developed using electron and packaged using electron-packager. I've been able to notarize the .pkg using the process described in the link in my first messageWhen the GUI application ("Dyalog 18.0") is launched it:starts the TCP server using the “net” module of electronspawns a "dyalog" process (via a bash shell) using the “child_process” module in electron. The "dyalog" process then connects back to the GUI app via TCP/IP.So, there is a deeper process hierarchy: (There's supposed to be an image here, but it appears to have disappered from the post).I've drag-dropped ALL of the processes between "Dyalog 18.0" and "dyalog" (inclusive) to "Full Disk Access" in "Security & Privacy" but I still can't get opendir to succeed in the "dyalog" process.There doesn't appear to be a way (as a user) to add Applications to the "Files and Folders" section of "Security & Privacy", (the + button is permanently inactive).I've added NSDocumentsFolderUsageDescription to the info.plist for "Dyalog 18.0" (is it OK to do that AFTER installation, or does it need to be in the .pkg'd version of info.plist?), and that hasn't helped.Many Thanks.John.