On Mar 20, 2021, at 5:53 PM, Keisuke Miyako via 4D_Tech <[email protected]> wrote:
> 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. Does the —deep option actually work anymore? The signing script I use for an app compiled with runtime has to sign every executable component in the built app. In any case, in order to make this work, Jorg will either have to completely re-sign and notarize a 4D app, which will likely require changing the bundle ID in the info.plist, which may actually prevent 4D from working. Or, do some development, build with Runtime, sign that runtime with appropriate entitlements, and test the signed notarized app to see if it’s working yet. This just the reality of accessing the camera in today’s world. Jim Crate ********************************************************************** 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] **********************************************************************
