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
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 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.
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
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.
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
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 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.
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
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.