On Mar 26, 2021, at 4:17 AM, Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com> wrote: > >> On 26 /03 /2021, at 22:03, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >> it is the app that needs to be notarised. >> >> the rules discussed so far are common to all apps, nothing is specific to 4D. > > I understand, it is totally my fault that it doesn’t work in > interpreted/debugging mode.
Not exactly your fault. Even if you were creating an app in Xcode you could specify camera access in the entitlements section, but it still wouldn’t work on 10.15+, and then you’d have to google, and eventually you might find the StackOverflow question with an answer specifying the necessary Info.plist keys you needed to add. There’s probably a page on the Apple developer documentation that indicates which Info.plist keys you need to add to access the camera but if it’s there is it’s easy to miss. I recently went through this when updating a macOS app; I’ve actually done all this before for a different app and I still ended up googling like a newbie doing it for the first time. The big difference is that this is not something those that develop only 4D normally have to deal with, and 4D’s built-in options for setting up app signing are somewhat lacking. Jim ********************************************************************** 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 **********************************************************************
