By the way, in synchronize.py", line 57 going to following line. sl = self._semlock = _multiprocessing.SemLock( kind, value, maxvalue, self._make_name(), unlink_now) I guess it is trying to reach a shared memory. there are some discussion about this SemLock method permission problems in internet but I could not find a proper solution in internet.

Thanks a lot for the response. I could solve the problem with following entitlements file and following codesign command. codesign -s "$SIGNING_IDENTITY_APP" --verbose --force --deep --entitlements /Users/emre/Documents/MrProtect/app.entitlements --options=runtime --timestamp --preserve-metadata=entitlements,requirements,flags,runtime \ I do not know which change worked exactly, but it is working now. app.entitlements.txt

I was entering the password into command which I entered into app-specific password window, but the correct password which will be produced automatically after my password entry . In the first 10 attempt it was not created. but then a new window popped up and showed me a new created password in such a format: ex: texe-crtt-wrrg-tftz this was working fine.

xcrun notarytool submit /Users/test/Downloads/test_launch_gui_stop_signed.pkg --progress --apple-id *** --password zzz --team-id yyy --wait giving also the same error

I archive to kill my camera with following command:"echo 1069 | sudo -S killall -SIGKILL UVCAssistant" But the camera cannot be switched on anymore, a reboot of macOS required. Does anyone an idea how I can start it again? PS:./UVCAssistant did not work. although I stared the process again, the camera cannot be started anymore

I solved the problem my self. With the reason that it was a communication between extension and my main app, I used UserDefaults to send the variables from SampleHandler to viewContoroller instead of calling a method. Thanks a lot for your support Claude31

Hi Claude31, Thanks a lot. It sound good. I will investigate isInUseByAnotherApplication. Best Regards Emre

Any résponse?

Hi, What a pity. Thanks a lot for answers.

Hi, is there anyone there?

Any response?

Any responses? I would be really appreciated.

@eskimo  Thank you very much for your fast and detailed response. Now it is clear to me, what is happening.  I will try a couple of hours to find a way to prevent that pyinstaller app calls (inherits) itself,  If I cannot find a solution then I will try further with py2app tool instead of pyinstaller to bundle my application. Thank you very much for your help.

@Etresoft:Thank you very much for your hints. Theys were really helpful to understand the problem in details. Answers are below for your questions: 1-Do you really want to do that?  Unfortunately, yes! Before I wasted several days to create my .app file via Pyinstaller, I was not aware of this sandboxing problem.  Therefore I want to research a couple of days more to solve the problem. 2-you are trying to Notarize with a Developer ID too? Actually It works fine somehow :) you can see in 9.Verification Of Certificate and sandboxing. But you can just ignore step9. When I was debugging my sandboxing problem, I saw that “spctl -a -t exec -vv test.app” command was throwing “rejected” error, therefore I thought that my problem could be relevant with this rejection. But apparently it is not :) 3-That GitHub link contains a reference to this person getting something close working I guess my problem is a similar one which you mentioned in your second link. During my researches, I found following description in Pyinstaller tutorial: PyInstaller Tutorial Bootloader Section - https://developer.apple.com/forums/content/attachment/8a6e87b3-8f02-4822-a837-5c770c7a668e So I had a look into my activity monitor(test.app without sandboxing, since sandboxed application crashes immediately), and I saw that they are 2 processes indeed: activity monitor view - https://developer.apple.com/forums/content/attachment/241f3a9f-3238-4851-bbf3-2eb97d83b784 Process id 8049 is parent of 8048. Could it be that I have to (somehow) inherit from my application itself for code signing?(<key>com.apple.security.inherit</key>) Maybe a similar situation as it is mentioned in your second link? Now "“Sandbox: test(8409) deny(1) forbidden-sandbox-reinit” error makes also sense. I tried to codesign my test.py with following inheritance entitlements: entitlements - https://developer.apple.com/forums/content/attachment/d44da246-9429-41c4-af47-12309b30db6d But unfortunately I got following crash report: crash report - https://developer.apple.com/forums/content/attachment/40143588-850e-4b63-92e1-f78f807d58fb Do you have any idea? Thank you very much in advance

@ eskimo:Thank you very much for your response. Your answers are below: 1-Does this generate a crash report? you can see my crash reports below: Crash Report1 - https://developer.apple.com/forums/content/attachment/b16a882f-9ccd-4c3a-b0e8-c3167ca69c94 Crash Report2 - https://developer.apple.com/forums/content/attachment/1b483ae6-7968-42b3-a112-9291ed0dadaa 2-Does the problem reproduce if you skip steps 7 through 9? Etresoft has also mentioned it. I guess it was a mistake to add these steps to my question :) you can just ignore step9. When I was debugging my sandboxing problem, I saw that “spctl -a -t exec -vv test.app” command was throwing “rejected” error, therefore I thought that my problem could be relevant with this rejection. But apparently it is not. Thanks a lot in advance.