Instruments is not honouring the working directory that I have specified in the target. It invokes the executable with the specified argument, but the working directory is root! ().
Needless to say this causes problems with my app. Changing the directory within the app doesn't work either. I have granted Instruments Full Disk Access rights within the Security and Privacy settings, but that makes no difference.
As a workaround, I attach to the already running process, but I'd like to know if this is a bug or if there is a trick to do this. XCode 13.1 and macOS 12.0.1.
Note that I had to codesign the executable to over come the "Failed to Get Authorization" error. See https://developer.apple.com/forums/thread/681687.
Thanks,
Stew
-
—
MCollett
Add a CommentI'm experiencing a similar issue with Xcode 14.2 on MacOS 13.2.1.The working directory from the Xcode scheme 'Profile' (a relative path) appears in Instruments target chooser (as the absolute path), but has no effect. In my case the actual working directory remains the default (i.e. the one containing the executable), rather than becoming root. The same working directory in the Xcode scheme 'Run' is used successfully, so it does look like an Instruments problem, not an Xcode one.