Program won't start on macOS when using the .app

[SimonSchroeder]

How do you run the program from the terminal? Do run the executable inside Contents/MacOS? Or do you type open MyApp.app?

If it is about not signing your app like @artwaw suggested, there is a difference to opening the app by just clicking on it (which will then not work) and doing a right click and selecting Open from the context menu.

[PatrickKox]

@SimonSchroeder
I run the executable in Contents/MacOS, when I use open MyApp.app it just ends without any message.

I've also tried to sign the app but that doesn't help.

[artwaw]

Out of curiosity, are you able to create fresh, new, simple program (can be just main window, empty), compile it, macdeployqt-it and run without any issues? Just to check if it is something particular to your main project that fails or the problem is in the environment itself?

[JoeCFD]

use dtruss to run your app to see what is missing. QtCreator has its own env settings. If your app can not be started, that means some env settings are missing. dtruss may be able to tell what.

[PatrickKox]

@artwaw
The blank project works fine, I don't even need to execute macdeployqt on it for it to work. So it's not my build environment.

@JoeCFD
dtruss returns a massive list of information, is there something I can grep at? Most information looks like memory addresses?

[JoeCFD]

@PatrickKox if a lib or plugin is missing, you may be able to see it. Pipe the output into a file.
and you can do the same thing by running the build with qtcreator which runs well. Then you can compare both output and may be able to find some hints.