I got the same result on the app after I ran it. The app does launch properly.
However, those changes happened after the app was downloaded.
-> codesign --verify -v T19.app
T19.app: a sealed resource is missing or invalid
file modified: /T19/T19.app/Contents/Database/T19.4DIndy
file modified:
Hi Jim,
I ran the following in Terminal to check it:
codesign -dv /Users/patbensky/CatBase\ dev/CatBase\ v8/Final\
Application/CatBase\ 8.app
and this is the result:
Executable=/Users/patbensky/CatBase dev/CatBase v8/Final
Application/CatBase 8.app/Contents/MacOS/CatBase 8
Are you sure the app is signed correctly? Sometimes an app with invalid
signature will launch until it is downloaded from the internet (downloading
sets the quarantine flag). I use these commands after signing to double-check
that signing worked properly:
spctl -av "$appPath"
codesign
compress the dmg (zip it) before uploading to dropbox?
On Wed, 24 Apr 2019 17:42:10 +0100, Pat Bensky via 4D_Tech wrote:
> Actually it doesn't seem to be working ... it seems to corrupt the app in
> some way.
> It's quite bizarre ... I compile the app, sign it using Miyako's code, and
> create a
Pat:
I use DropBox for this every week. When I bill a .dmg file I upload to Dropbox
and for about that last 6 months, when it is downloaded by others it works fine.
Just of note I use DMG Canvas. That should not matter, but it is a point of
difference.
Jody
> On Apr 24, 2019, at 10:42 AM,
Actually it doesn't seem to be working ... it seems to corrupt the app in
some way.
It's quite bizarre ... I compile the app, sign it using Miyako's code, and
create a disk image using DropDMG. I check it by mounting the disk image
and installing the app. It runs OK.
Then I upload it to DropBox.
Brilliant, thank you Miyako!
Note that I needed to make one change to the code, in the method "code
sign":
Change
$infoPlistPath:=$applicationPath+Folder separator+\
"Contents"+Folder separator+"Info.plist"
to
$infoPlistPath:=$applicationPath+\
"Contents"+Folder separator+"Info.plist"
Pat
the text edit setting "smart dashes" may convert double hyphens to dash,
which is not what you want in this context.
https://support.apple.com/kb/PH23628?locale=ja_JP=en_US
a single hyphen must be used with a short option name (-f)
a double hyphen must be used with a short option name (--force)
Hi Jody,
Yes, I thought that might be an issue so I made sure that the pathname had
no spaces, to test it - IE:
/Users/patbensky/Desktop/catbase/CatBasev8b105.4DB
I still get the "No such file or directory" error when I try to run the
code sign code, but it I run simple code to open the file ie:
Pat:
The error No such file or directory, is an error saying that the paths you are
giving Terminal are incorrect. One thing that can cause this is if the file
name, or the directory path has spaces in the names. Though the OS can handle
spaces terminal cannot. You need to put an escape
Hi Jeremy,
I've tried different hyphens ...
--force --deep
I get:
ID: No such file or directory
-force -deep
I get:
invalid argument "rce"
?
On Tue, 2 Apr 2019 at 19:56, Jeremy Roussak via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Pat, what’s the character before “force”? In your email,
Pat, what’s the character before “force”? In your email, it seems to be an
em-dash. I suspect it should be a double-hyphen. The same will apply to the
character before “deep”.
Jeremy
> On 2 Apr 2019, at 19:05, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> wrote:
>
> Hi Jody,
> Thanks very
Hi Jody,
Thanks very much for this.
I've tried running doing as you suggested in Terminal but I always get:
Developer: found in both
/Users/patbensky/Library/Keychains/login.keychain-db and
/Library/Keychains/System.keychain (this is all right)
—force: No such file or directory
The pathname for
Thanks Jody - I will try that.
Pat
On Thu, 21 Mar 2019 at 14:17, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com>
wrote:
> Pat:
>
> I struggled with this for a few months. A bunch of research, help from the
> nug, and help from 4D Tech support, I think I found our problem. We will
> use a graphic
Pat:
I struggled with this for a few months. A bunch of research, help from the nug,
and help from 4D Tech support, I think I found our problem. We will use a
graphic application to create some graphics (icons / pictures etc). As is
usual, Apple is getting more strict with each version of the
Using v17
I've added our Apple OSX signing certificate to a client's app built with
4D v17. It compiles and runs just fine.
I've added the same certificate to another app, using the same version of
4D and the same compiler settings. However with this one, at the end of
compilation, I get the
16 matches
Mail list logo
