Xcode Project Won't Build

I exported my game to an Xcode project.

At first I got this error with Build Haxe:

Code: [Select]

ExternalBuildToolExecution failed with a nonzero exit code
I've read that if you delete the Build Haxe target, that should fix the issue. But when I delete that target I get a new error

Code: [Select]

Library not found for -lApplicationMain
I am on macOS Catalina, using Xcode 11, and Stencyl 4.0.1 b10449

I'll add that I also tried publishing and uploading my IPA file via Transporter. I get this error:

Code: [Select]

ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: 'true' for the key 'get-task-allow' in 'Payload/poorthief.app/poorthief'."

I'm currently using b10468, and it publishes fine. However I need to have both IAP and Unity Ads disabled.

If you download Stencyl fairly recently, you may have gotten a version that has an issue installing Neko. can you compile for any other platform at all? If so, that's no the issue. But if that is the issue, download b10470 or later (the current subscriber's build) and try again.

Did you open Xcode through Stencyl, using Tools > External IDE > Launch Xcode? If not, please open Xcode in this way because it allows it to use the same build environment that Stencyl does. Then, to build in Xcode, select the default target (it should be the name of your app), not "Build Haxe". However, don't delete "Build Haxe" either. That's a workaround that you don't need if you open Xcode through Stencyl.

Hey Justin,

I think opening Xcode via Stencyl was the key. I got it to build no problem.

Thanks for the insight!

Tom

One further question. I get a crash in my Testflight build, I ran the game in debug mode and I found the issue. But I can't figure out what object has ID 8.

Attached is my Game Controller log.

If you run the game in debug mode it should give you more info, showing you the behavior that's coming from. (I'd suggest testing in Flash or HTML5 since they're automatically debug mode and will compile faster.)

Good idea. I was able to find the missing resource, it was an unassigned font.