I’ll use the terminal to sign what ever has to be signed that enables me to continue developing: codesign --deep --force --verbose --sign "<Developer ID Application: Jorg Knebel (******)>” $Path/To/My/Development
the above code unfortunately will not grant access to the camera because it is missing 2 critical elements: 1. edit "info.plist" to explain what the app needs the camera for 2. supply an entitlements file that will be embedded in the code signature for examples see https://github.com/miyako/4d-utility-build-application in addition, the use of "deep" (sign from the outside in) and "force" (over-write existing signature of plugins and frameworks) can work against your objective. again, the above example shows how to sign from the inside out. 4D itself does not need access to the camera in order to fully function, it is understandable that 4D does not have the permission by default. it is not just Apple, the world's view on privacy and surveillance has much evolved in the past decade. ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
