CLI 2 not connecting to desktop app; unable to determine parent process

Aha! Everything works fine in Terminal, but not in iTerm. Checking into what shell differences I might have setup...

I am having the same issue with iTerm2, did you figure out a fix for it @farmallfan ?

No, not yet, sorry... Once we had the workaround of using Terminal, we grabbed that and kept going. Would prefer iTerm though. Oddly enough, others in the org who run iTerm did NOT have the issue, so it's likely something in the configuration.

Is a solution already known here? I have the same error.
iTerm: "connecting to desktop app: determining parent proces of 34048: operation not permitted"
Terminal: is working

@farmallfan I updated to the newest iTerm2 and it works for me now.

Hey all, indeed, updating iTerm2 seems to fix this issue, in some cases.
Can you please confirm whether upgrading to the latest version (3.4.15, at the moment of writing, on the stable channel) fixes the issue?
Thanks!

Best,
Horia

I've updated iTerm but it's still not working for me.

Thank you for your followup! I understand that the error is something along the lines of:

connecting to desktop app: determining parent process of <pid>: operation not permitted


Can you please share what process has the ID? You can find that using ps aux. This will help us debug as we'll know whether it's going to far up the parent tree or whether there's another problem.

Also, if you are willing to install pstree (brew install pstree), that would be even more helpful.

In that case, if you can first run the op command and copy the error message and then immediately run pstree -w -p $$, that would be of great help. Then we have the full process tree and the PID of the process that is causing the problem.

Looking forward to hearing back from you!

Best,
Horia

Having the same issue with the latest iTerm2 and M1 MBP. Any progress on the solution?

The process PID for me points to this:

Hey @fiddler. Thank you for reporting back with that extra context. That gives me an idea as to what is happening and I have been able to reproduce the problem in one way. We're working on a fix.