Re: [4D v18.3; Mac {10.13.6} + {10.15.7}] LEP-voodoo

[Keisuke Miyako via 4D_Tech]

info.plist and entitlements are 2 different entities.

the com.apple.security.device.camera key needs to be in entitlements, not 
info.plist.
info.plist is where you add NSCameraUsageDescription.

if you use a code editor to edit either plist file,
you might want to "plutil -convert xml1" to normalise the file first.
in general, using a tool other than Xcode will invalidate the plist file.

but again, all of that is done automatically in the GitHub example I shared 
earlier.
you just have added your Apple Developer password to keychain for it to work.

https://miyako.github.io/2019/06/17/notarization.html
**
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:4d_tech-unsubscr...@lists.4d.com
**

Re: [4D v18.3; Mac {10.13.6} + {10.15.7}] LEP-voodoo

[Jörg Knebel via 4D_Tech]

Hi Jim

> On 25 /03 /2021, at 13:31, James Crate via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> So if Jorg wanted to change the entitlements on the 4D.app he uses for 
> development so it could access the camera, he could just re-sign with the new 
> entitlements and his developer ID and notarize a copy of 4D.app with the 
> bundle ID "com.4d.4d”? I never tried this but I just assumed notarization 
> would require a different bundle ID. I guess the combination of bundle ID + 
> developer ID would still be unique, but I guess I just assumed that Apple 
> wouldn’t let that happen.
> 
> Btw, I’m pretty sure camera access requires entries in info.plist in addition 
> to the entitlements but I guess that’s probably already been covered.  It’s 
> also worth noting that the “4D.entitlements” used by 4D’s SignApp.sh has 
> com.apple.security.device.camera set to true so theoretically the only extra 
> thing needed should be the info.plist keys and a built signed notarized app 
> should be allowed to access the camera.


Thanks for sharing your thoughts.

Nothing I tried worked so far.

So, my last attempt to get Keisukes PlugIn working now is to clean my Catalina 
Mac of everything 4D an than reinstall v18.

If this is done I’ll extend the entitlements of 4D by adding the needed pieces 
into the info.plist by using BBEdit eg.


com.apple.security.device.camera



After that, I’ll see if it works within my development (Binary Mode).

I might sign my *.4DB via the terminal.

Cheers
Jörg
**
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:4d_tech-unsubscr...@lists.4d.com
**