Mac App not starting

I’ve had a couple of support calls recently from people who double click my app and nothing happens.

There’s at least 10 installs per week - I am confident that there isnt a ‘missing file or NOE’ exception happening.

Has something changed in the OS that means MacOS is getting even more fussy (if that was possible!!!)

Codesigned & Notarised as you would expect.

Is it new fresh instal of your app or an already installed app starting correctly previously ?

Is it an Intel or ARM build ? If the first, is Rosetta installed ?

Does the app make it to the first line of code? Does your app write any files or read any files? You can add a line for the Console at the first line of code. Is anything else visible in the Console?

Do you use AppleScript when the app is starting?

Looking like user error or iCloud sluggishness.

Just had a message to say ‘its open now’, without answering any of my own ‘tell me x,y,z’ questions.

:slight_smile:

For the questions above,

fresh install, universal build, no Applescript, clearly makes it to the first line of code (but I’ll look into that as a future debugging tool, thanks!)

I had last year a similar problem. After much tests I found that macOS thought that my application has a virus. Although it was notarized. Finally I was able to solve it with changing the optimization level.

2 Likes

@Manfred_Richter - out of sheer curiosity, changed the optimization level how? Increased it? Decreased it?

Anthony

I increased it. But maybe decreasing also helps. I believe the compiler creates a bytes in sequence that the virus scanner detects a virus. With changing the optimization another sequence will be created.

1 Like

How did you find that out?

I have been experiencing the same issue ever since I moved to Tahoe (26.2). I have been putting off releasing an updated version of my app tailored for Tahoe. However, I have found that if I re-codesign and re-notarise the app (I use App Wrapper), I can open it again. This is obviously not a long-term solution. I looked at the logs, but found no information relating to the app launch. I really do not know what is happening.