pkg'd version of ist?), and that hasn't helped.Accessibility access to control your computer is required to use many features including selecting menu items, manipulating windows, pressing buttons, typed string triggers and the window switcher. I've added NSDocumentsFolderUsageDescription to the ist for "Dyalog 18.0" (is it OK to do that AFTER installation, or does it need to be in the. 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 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. So, there is a deeper process hierarchy: (There's supposed to be an image here, but it appears to have disappered from the post). The "dyalog" process then connects back to the GUI app via TCP/IP. spawns a "dyalog" process (via a bash shell) using the “child_process” module in electron.starts the TCP server using the “net” module of electron.When the GUI application ("Dyalog 18.0") is launched it: pkg using the process described in the link in my first message The GUI application (Dyalog 18.0) is developed using electron and packaged using electron-packager. When running interactively inside Termimal, and "dyalog" calls opendir, Terminal pops up with "Teminal eould like to access files in your Documents folder"). 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") The system put up the expected approval alert and, once I approved the access, the app printed a listing of the Documents directory.Īpple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = "eskimo" + "1" + Eskimo, Thanks for responding.Īs you suspected, the configuration is more complicated than I implied in my first post - perhaps I oversimplified. In the storyboard, I added a button and wired it up to that method. NSURL * docDirURL = URLForDirectory:NSDocumentDirectory inDomain:NSUserDomainMask appropriateForURL:nil create:false error:NULL] ĭIR * dir = opendir(docDirURL.fileSystemRepresentation) I added the following method to the ViewController class: I added an NSDocumentsFolderUsageDescription entry to the ist. If it is, that’s a whole different kettle of fish. I’m presuming that your app is not sandboxed. In the Signing & Capabilities editor, I removed the App Sandbox slice. Using Xcode 11.2 on macOS 10.15, I created a new app from the macOS > App template, selecting Objective-C for the language and Storyboard for the user interface. I tried this here in my office today and it worked just fine. In terms of GUI apps, there should be nothing to stop you from enumerating the Documents directory using C APIs. So, is this a GUI app? Or something else, like a command-line tool, that’s not a GUI app but is an application in the general sense? You’re not talking about a GUI app, but instead using the term “application” in a more general sense Your app has a C core with an Objective-C outer shell You will need at least some Objective-C (or Swift) for the outer shell. It’s not possible to write an macOS app in C. I’d like to start by clarifying the above. Is there an API I should be calling to provoke the dialog and to grant the requred permissions? None of these things allow opendir to succeed (and none them result in a dialog containging " Would like to access files in your Documents folder"). To make sure that the bundle is properly notarized.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |