Now there's a crash report though
Sadly, that’s not useful. I misread your original post and sent you down the wrong path here. Re-reading that post it’s clear that you’re doing the iOS Apps on Mac thing, and I wouldn’t expect you to be able to run such an app from Terminal.
My apologies.
As to what is going on here, it’s hard to say. In general iOS Apps on Mac are meant to Just Work™ — within the documented constraints of that feature — and there are no knobs for you to twiddle.
Earlier you wrote:
the next message that's in the console about the app after the
messages stating its launched is:
… termination reported by launchd (0, 0, 256)
That 256 is interesting. I dug into the log message and it seems that this value is a wait status, as returned by system calls like waitpid. If you look at the waitpid man page, you’ll see there are macros to decode such values. Consider:
int status = 256;
fprintf(stdout, "WIFEXITED: %d\n", WIFEXITED(status));
fprintf(stdout, "WEXITSTATUS: %d\n", WEXITSTATUS(status));
So it seems your app has called exit with a value of 1, aka EXIT_FAILURE.
It’s rare for framework code to exit your app in this way. Most of the time when a framework decides it’s time to terminate the process, it traps in some way, and that generates a crash report. Sometimes a framework might call exit with 0 due to normal termination.
My best guess is that some third-party code within your process — your code, or code from one of the third-party libraries you’re using — has detected a problem and called exit. Try this:
-
Build your app for the device.
-
Find all the Mach-O images within the app:
% find MyApp.app -type f -print0 | xargs -0 | grep Mach-O
% find MyApp.app -type f -print0 | xargs -0 file | grep Mach-O
MyApp.app/MyApp: …
-
Search each one for calls to exit:
% nm MyApp.app/MyApp | grep exit
and its low-level equivalent _Exit:
% nm MyApp.app/MyApp | grep _Exit
Any hits?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
