Another macOS Codesigning/Notarization issue

[J. Landman Gay]

The uninformative error dialog is what I got when the app was corrupted but 
I doubt that's the problem for yours. But if code signing is the issue you 
usually get a different dialog with a reason.

Have you tried Matthias' helper tool? Once I fixed my app it worked 
perfectly. You can download it from the link at the top of the lesson page, 
the one for Xcode 13+. t does use notarytool.

--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 15, 2023 4:01:05 PM Paul Dupuis via use-livecode 
<use-livecode at lists.runrev.com> wrote:

> Help,
>
> I am trying to switch Notarization tools for the Apple November
> deadline. I was using macOS Mojave with Xcode 10.2.1 and not (to use the
> new mandated Notary tool) have to move to Sonoma with Xcode 15.0.0.
>
> I have signed, notarized, and stapled (all responses returned were what
> the lessons at Livecode.com by Matthias said they should be) a Livecode
> 9.6.10 Standalone using my Mojave system (the old tool) and it works on
> Sonoma and Mojave
>
> I have signed, notarized, and stapled (all responses were as the lesson
> said they should be) a Livecode 9.6.10 Standalone using my Sonoma system
> (the new tool) and I get  an error trying to run it on Sonoma. It runs
> under Mojave (although the first time the cursor spins a lot and it
> takes a while to start)
>
> The error is an extraordinary helpful dialog with a smiling macOS icon
> that say 'The application "<appname>" can't be opened." and an OK button.
>
> I though for a bit that it was that I was still building for Intel and
> the Sonoma is a M1 macBook Air, so I changed the Standalone settings and
> redid everything (again all seemed okay) and the GetInfo says Universal
> (where it said Intel before) but I get the same message.
>
> AGAIN, the old Notarization procedure produces an notarized (and
> stapled) app (that is actually just Intel) that runs without error on
> Sonoma on M1 MacBook Air and Mojave on Intel Powerbook, but the new one,
> from the lessons for Xcode 13+ produced the error above and my app will
> not run.
>
> Security is set to allow App Store and Identified Developers.
>
> Unless I figure this out, I will not be able to make new version of our
> macOS app after November 1. Has anyone else experienced this? Has any
> one see this message?
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode