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

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

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

> 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

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

actually the database kind doesn't matter, there is nothing to do for the structure file or project. it is the app that needs to be notarised. the rules discussed so far are common to all apps, nothing is specific to 4D. ** 4D

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

> On 26 /03 /2021, at 17:41, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > info.plist and entitlements are 2 different entities. Just to clarify one thing: You are talking about “4D Project Mode” all the time, do you?

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

Keisuke, > On 26 /03 /2021, at 17:41, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > info.plist and entitlements are 2 different entities. Now I’m totally confused. Where is the “entitlement entity” located? I asume it too should be edited with Xcode only? I never touched

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

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

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

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

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

the "--primary-bundle-id" you pass to "xcrun altool" is actually unrelated to the app's bundle id; it can be any string and it does not have to unique. 2021/03/25 11:31、James Crate via 4D_Tech <4d_tech@lists.4d.com>のメール: just assumed notarization would require a

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

On Mar 24, 2021, at 6:09 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > >> 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. > > yes it works. > I use --deep to

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

> 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. yes it works. I use --deep to sign every framework, bundle, plugin from the inside out. think of it like sealing smaller boxes

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

On Mar 20, 2021, at 5:53 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> 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

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

Wayne, Just for your information. > On 21 /03 /2021, at 00:41, Wayne Stewart via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > You don’t need to as far as I know. > > A .4db is just a document. > > It’s only the application that needs to be signed. Maybe plug-ins as well > I’m not sure, but

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

Hi John, Thanks for sharing your procedures. > On 22 /03 /2021, at 03:31, John J Foster via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hope that helps. If not ask away and I’ll try to remember how I got this all > working. It took me time. Yes it helped. Finally I have an idea where the

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

Hi Jörg, Like wayne said! You have to sign everything required to work with your application: 4D, plugins, folders included, resources, etc. In my case I hand a standalone engined app for Mac and Windows. I build my standalone 4D app. I then use Miyako’s BUILD application (or you can move

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

> On 21 /03 /2021, at 18:05, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > like I posted earlier, all the steps are implemented in the example: > > https://github.com/miyako/4d-utility-build-application > Yes of cause.

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

like I posted earlier, all the steps are implemented in the example: https://github.com/miyako/4d-utility-build-application 2021/03/21 15:41、Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com>のメール: Could you offer a step by step explanation because this is all new to me.

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

> On 21 /03 /2021, at 11:53, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > 1. edit "info.plist" to explain what the app needs the camera for Do you mean the 4D info.plist? > 2. supply an entitlements file that will be embedded in the code signature Entitlements file?

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

I’ll use the terminal to sign what ever has to be signed that enables me to continue developing: codesign --deep --force --verbose --sign "” $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"

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

Wayne, > On 21 /03 /2021, at 00:41, Wayne Stewart via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > You don’t need to as far as I know. Not according to Keisuke: > On 07 /03 /2021, at 13:59, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com > > wrote: > > I will

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

Jörg, You don’t need to as far as I know. A .4db is just a document. It’s only the application that needs to be signed. Maybe plug-ins as well I’m not sure, but not the .4db Wayne On Sat, 20 Mar 2021 at 23:30, Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com> wrote: > Hey Champion, > > > On 07

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

Hey Champion, > On 07 /03 /2021, at 13:59, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > yes, it does not matter if you are in development or production, compiled or > interpreted. > access to the camera requires entitlements, code signature, notarisation, and > not of the

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

Keipsuke, > On 07 /03 /2021, at 13:59, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I will answer in place of Armin; > > yes, it does not matter if you are in development or production, compiled or > interpreted. > access to the camera requires entitlements, code signature,

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

I will answer in place of Armin; yes, it does not matter if you are in development or production, compiled or interpreted. access to the camera requires entitlements, code signature, notarisation, and not of the plugin, but of the app (4D) itself. Since Keisukes Cupturev2-Plugin does not work

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

Hey Armin, > On 06 /03 /2021, at 07:38, ADeeg via 4D_Tech <4d_tech@lists.4d.com> wrote: > > you have to sign and notarize your mac app with the Magic Miyako tool build > application to enable the needed security settings and get the camera > access. Even if I’m still at the

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

4D Tech mailing list wrote > Everyone, > > Many thanks for the answers and the tips, it was very helpful. > > I followed up on all the tips and tricks > > • “./“ Yes and no > • $MyShellScript.sh > - hard coded in BBedit > - created in 4D >

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

Everyone, Many thanks for the answers and the tips, it was very helpful. I followed up on all the tips and tricks • “./“ Yes and no • $MyShellScript.sh - hard coded in BBedit - created in 4D - chmod 755 $MyShellScript.sh

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

Peter, > On Mar 4, 2021, at 10:03 AM, Peter Bozek via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > On Thu, Mar 4, 2021 at 1:59 PM Jörg Knebel via 4D_Tech > <4d_tech@lists.4d.com> wrote: >> >> $FoDoPath:=Get 4D folder(Current resources folder) >> $FoDoPath:=Convert path system to

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

On Thu, Mar 4, 2021 at 1:59 PM Jörg Knebel via 4D_Tech <4d_tech@lists.4d.com> wrote: > > $FoDoPath:=Get 4D folder(Current resources folder) > $FoDoPath:=Convert path system to POSIX($FoDoPath) > > $cmd:=$FoDoPath+"./imagesnap -w 2.0 " Jörg, what seems suspicious to me is the "./" in above. "./"

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

Hi Jörg, I had a very old version in Imagesnap in one of my projects but it doesn't work any more. Using this old version 4D always hangs. Unfortunately updating to the latest version did not help. No more hang, but no image data returned. Thus far I suppose it's an issue of privacy setting.

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

Jorg, not directly related... but... when I was F-ing around with LEP trying to get a file manipulator working, on Windows the command xcopy gave me the same sort of result the command line when supplied to the command prompt worked. when supplied through LEP failed. Now again, not Mac, and not

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

G’day All, We are talking Mac ONLY - High Sierra and Catalina! I found a command line application that can take a snapshot with the current camera. This nifty tool is called “imagesnap” and it is totally free in all regards. Check out: http://iharder.sourceforge.net/current/macosx/imagesnap/