Post

Replies

Boosts

Views

Activity

NSTask-launch path not accessible
I'm trying to launch a command line app from my objective C application (sandboxed) using NSTask and I keep getting "launch path not accessible" Here is the path: [task setLaunchPath:@"/usr/local/bin/codeview"]; I have set the appropriate attributes for codeview and it is working perfectly when I use it from the command line and /usr/local/bin IS in the $PATH I know I have NSTask configured correctly because this WILL work: [task setLaunchPath:@"/usr/bin/hexdump"]; With the exception being that I'm using a command already in /usr/bin. But I can't copy codeview into /usr/bin due to SIPS. I've tried moving codeview to various other non-SIPS protected locations all to no avail. Must all NSTask commands come from /usr/bin? Where might I put codeview so that it can be launched. Today I'm going to use an older computer and disable SIPS to put my command in /usr/bin and see if that works. If it does. I will do it on my main machine.
6
0
168
Apr ’25
Trader status and app updates
Hi. I am a indie/hobby developer that has a "for purchase" app in the App store and from what I can tell from the legalese that makes me a trader. I plan to simply de-list from the EU market, because I don't want my personal information displayed, and I don't make enough money off the app to warrant setting up a LLC, or PO box etc. Will customers in the EU who have ALREADY purchased my app prior to de-listing still receive any updates I make to the App or are they gonna be SOL?
1
0
532
Jun ’24
WkWebview crash
Created an objective C app that has an embedded wkwebview. I am using the loadHTMLstring to display a NSString created by the application, no external links are used (although it will load them). When launched from Xcode in debug mode, the program works as intended. When I build a signed distribution package, it will work on the computer that built it. But when I take that build to another computer, the app will crash upon launch, not even opening the dialog. The crash log indicates that it is due to wkwebview. Running macOS 11.2.2 on both machines, (last week 11.2.1). I have the proper webkit library and framework linked. Any thoughts.
1
0
760
Mar ’21