I am attempting to construct functions utilizing my very own construct system, exterior of Xcode. I’ve obtained issues operating on my macOS laptop computer (x86) and on iOS units (ARM), however I have never but run my app within the iOS simulator. The error that comes again is unhelpful, and I’m wondering if anybody is aware of tips on how to discover out what’s incorrect.
I compiled the app for my host structure (x86_64), utilizing the simulator SDK (/Functions/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.4.sdk). And I ran the codesign utility on it. So I’ve a bundle able to go in Hi there.app. Subsequent I run these shell instructions:
# Begins the simulator
% open /Functions/Xcode.app/Contents/Developer/Functions/Simulator.app
# Set up app on the simulator
% xcrun simctl set up booted construct/HelloWorldIOS/Hi there.app
# Attempt to launch it
% xcrun simctl launch booted com.instance.HelloWorldIOS --console -w
An error was encountered processing the command (area=NSPOSIXErrorDomain, code=3):
Simulator gadget returned an error for the requested operation.
No such course of
Underlying error (area=NSPOSIXErrorDomain, code=3):
Utility launch for 'com.instance.HelloWorldIOS' didn't return a legitimate pid nor a launch error.
No such course of
The app icon expands to a black display for a second, so I do know it is attempting to launch it. Nevertheless it disappears instantly.
I have never discovered something useful within the Console.app logs. There are many messages about as useful as this:
Bootstrapping failed for <FBApplicationProcess: 0x7fb57d670960; software<com.instance.HelloWorldIOS>:<invalid>> with error: <NSError: 0x60000033e820; area: RBSRequestErrorDomain; code: 5; purpose: "Launch failed."> {
NSUnderlyingError = <NSError: 0x60000033f330; area: NSPOSIXErrorDomain; code: 162>;
}
The primary strains of my predominant() operate attempt to write to stdout and stderr, so both it is not getting there, or --console would not do what I assumed it will do.
