Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-28 Thread Jeremy Roussak via 4D_Tech
That’s really useful, Miyako. Thanks. Jeremy > On 28 Nov 2018, at 08:58, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > the target path can be found in the build project > > for instance, in this example, the path is accessible with the code > > If (Is macOS) > $path:=$BuildAp

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-28 Thread Keisuke Miyako via 4D_Tech
the target path can be found in the build project for instance, in this example, the path is accessible with the code If (Is macOS) $path:=$BuildApp.BuildMacDestFolder Else $path:=$BuildApp.BuildWinDestFolder End if $path:=$path+"Final Application"+Folder separator https://github.com/miyako/4d-c

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-26 Thread Jeremy Roussak via 4D_Tech
> On 20 Nov 2018, at 15:27, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Is there an easy way to get the file path to the built client and > server apps for the command line? > Not that I know of. I have it hard-coded, which means that it breaks if I fiddle with it. So I don’t

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-20 Thread Dave Nasralla via 4D_Tech
Thanks Jeremy, I like your idea of integrating into your build code. I saw an old tech note on that, but it seems out of date. I am currently using an Applescript for code signing: set theDocument to choose file with prompt "Select the 4D Client application:" set filepath to POSIX path of theDocu

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-20 Thread Jeremy Roussak via 4D_Tech
Dave, FWIW, I found information on signing hard to unearth and harder to understand. Eventually, I managed to sign my compiled application using these commands at the end of my build method: LAUNCH EXTERNAL PROCESS("xattr -cr "+$appPath) LAUNCH EXTERNAL PROCESS("codesign --deep --forc

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-19 Thread Dave Nasralla via 4D_Tech
Here is a followup for what I did. I created and Applescript to remove the quarantine attribute from the downloaded client: set theDocument to choose file with prompt "Select the 4D Client application:" set filepath to POSIX path of theDocument do shell script "xattr -d com.apple.quarantine \"" &

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-19 Thread cjmiller--- via 4D_Tech
If I am building internal apps that do not get distributed over wan. Is this something I need to be concerned with? Thanks and regards Chuck Sent from my iPhone > On Nov 19, 2018, at 2:36 PM, Dave Nasralla via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Thanks Keisuke. Is there information

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-19 Thread Dave Nasralla via 4D_Tech
Thanks Keisuke. Is there information on signing a built app? We did find the command xattr -d com.apple.quarantine filepath but if signing the app will work, I'd like to do that. dave On Mon, Nov 19, 2018 at 11:57 AM Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > the information ab

Re: Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-19 Thread Keisuke Miyako via 4D_Tech
the information about where a file was downloaded from, is stored in extended file attributes. it had nothing to do with code signature or md5 checksum. if necessary, you can clear it with cli xattr -rc you can sign a built app from the cli or from 4D, but in addition to that, you need to sign

Transferring Build Mac Client via Google Drive Web Interface Fails

2018-11-19 Thread Dave Nasralla via 4D_Tech
Hey All, For a long time we would distribute our built mac clients via google drive using the google drive web interface. We simply zip the built client and upload. Since the auto-update feature works quite well we haven't used it recently. Until today: - I have a working built client - I zip t