LiveCode Forums

When I attempt to open the downloaded unzipped Mac standalone version of my app I get "<app name> is damaged and can’t be opened." Baffling factors:

* The app runs fine before zipping and after unzipping without downloading.
* The Windows version of the same app unzips and runs fine after downloading.
* The Mac version of another very similar app also unzips and runs fine after downloading.

I've looked for differences I might have inadvertently set in Standalone Application Settings, but without result.

I appreciate any insight about the possible cause of this problem. Thanks!

It's likely a code-signing issue.
Have you code-signed and notarised your standalone app?

If not, have a look here: https://lessons.livecode.com/m/4071/l/1 ... c-appstore

Hope that helps,
Stam

Thanks, I'll look into that. Rookie here. I was aware of those processes but thought they were relevant only to iPhone apps.

It's likely a code-signing issue.

I do not think I believe that.

I just ran off a Mac 64-bit standalone from LC 8.1.10 on my 32-bit 2006 iMac running MacOS 10.6.8
and carried it over to the other side of the room on a flash-drive and copied it onto the desktop
of my 2018 Mac Mini running MacOS 12.3 and the thing opened "just like that". . . no code signing,
no nothing.
- -
I wonder if your problem has got something to do with the ZIP compression?

Should you wish to try this, my standalone (zipped on MacOS 12.3) is available here:

https://www.dropbox.com/s/lngzju35ch4tpc7/TEMU.zip?dl=0

As I said in my original post, "The Mac version of another very similar app also unzips and runs fine after downloading." So code signing and notarizing don't appear to be causes of the problem.

Both apps were zipped in the same fashion, and I have re-zipped the problem app without a different result, but I suppose I could continue looking into that.

I have also downloaded from multiple sites (Google Drive, Dropbox, OneDrive) without success.

richmond62 wrote: ↑

Fri Mar 18, 2022 2:21 pm

I do not think I believe that.

Richmond, you are of course welcome to actually provide a better explanation. Please note that the crucial step here is the downloading. Copying from usb drive probably does not replicate the issue.

I mention this as this is what affected me, and what may be affecting @bd525...
In my case - to be specific - i created the standalone -> no problem.
Zipped -> no problem.
Uploaded the zip file and then re-downloaded -> problem.
Problem solved by code-signing.

Seems to me likely the same issue. You lose nothing by code-signing. Notarising on the other hand may cost you the annual apple dev fee (or maybe not, i'm not sure).

Hope that helps
Stam

richmond62 wrote: ↑

Fri Mar 18, 2022 2:21 pm

Should you wish to try this, my standalone (zipped on MacOS 12.3) is available here:

https://www.dropbox.com/s/lngzju35ch4tpc7/TEMU.zip?dl=0

Too bad...
I love it when a good theory falls apart

Interesting . . .

1. Mind you, you might like to try a right-click and see what the drop-down menu says . . .

2. Can anyone explain why my walk across my study (as per previous post) caused no problems?

Please note that the crucial step here is the downloading.

Oh, "Sugar" . . . downloaded my own thing:
- -
Right-Click did the trick:
-

My problem app works fine when transferred between devices by physical media (USB), in either zipped or unzipped form. The problem only occurs when a zipped version is downloaded online. And again, another app--also not code signed, and with identical Livecode standalone application settings--works fine after zipping and downloading.

Have you tried Right-clicking the app?

Yes, same result: "“<app name>.app” is damaged and can’t be opened.

You in a right pickle then.

As I find that MacOS 12 will let apps 'in' with a right click.

I suppose one of the question that need to be asked refers
to the 'extra' bits one can select in the standalone builder to be rolled up into one's standalone.

The "developer cannot be verified" is specifically a code-signing issue. Gatekeeper throws that error if the app has not been notarized. Was the one that does work created in a previous version of Mac OS? Older apps are grandfathered in.