Thank you so much for the response! There are two applications, the old server, and the new client. The task is to receive the data from the remote server using events. They have long been implemented on the server and the old client. As part of the improvement work, it was decided to use async events. I got errAEPrivilegeError when I tested it with the old server and new client. The decision was made to create 2 separate applications to isolate the environment (sender and handler). In the case of the old server, problem number one does not exist. I would like to know why the server machine does not ask for credentials. (application in release) A new receiver in the debug, sending the answer asks for credentials. And the main problem is errAEPrivilegeError. I see that I receive the response event, but I cannot handle it. {aevt,ansr target=aprl(34/$657070633a2f2f3139322e3136382e302e37362f48656c697825323053657276...) {----=utxt(24/$38002e0039002e0030002000280038003900300031002900)} returnID=17537} 2023-02-28 11:08:42.162016+0200 Run[6739:57168] [main] AppleEvents/sandbox: Returning errAEPrivilegeError/-10004 and denying dispatch of event aevt/ansr from process ''/0x0-0x0, pid=0, because it is not entitled to send an AppleEvent to this process. But other events sent not by the response (aevt,ansr) - I get. I also get the same code on the same machine by bundle id. I also receive them by sending them with the waitForReply send option.

Hi Thank you for the response and for the provided information. I cleared the entitlement. Bundle id works. The error is still here with sending by eppc.

Hi there, The sender is sandboxed. The sender and target applications are under my control. In case of sending by bundle іdentifier: I already set com.apple.security.app-sandbox to false because I got an error procNotFound -600  in the receiver. Also com.apple.security.scripting-targets or com.apple.security.temporary-exception.apple-events solves this problem. When sending by eppc - I still get errAEPrivilegeError/-10004\ parallel