UATHelper: Packaging (IOS): ---- Starting trace ----
UATHelper: Packaging (IOS): UbaSessionServer - Disable remote execution (remote sessions will finish current processes)
UATHelper: Packaging (IOS): ------ Building 4 action(s) started ------
UATHelper: Packaging (IOS): Took 12.24s to run dotnet, ExitCode=138
UATHelper: Packaging (IOS): UnrealBuildTool failed.
UATHelper: Packaging (IOS): AutomationTool executed for 0h 0m 23s
UATHelper: Packaging (IOS): AutomationTool exiting with ExitCode=138 (138)
UATHelper: Packaging (IOS): RunUAT ERROR: AutomationTool was unable to run successfully. Exited with code: 138
PackagingResults: Error: AutomationTool was unable to run successfully. Exited with code: 138
LogStreaming: Display: FlushAsyncLoading(411): 1 QueuedPackages, 0 AsyncPackages
PackagingResults: Error: Unknown Error
Hello there @jppaceman!
From what I could gather around the community, this type of error (138), usually pops up in cases of bad memory access, or plugin conflicts (the most likely case).
To tackle this one, it boils down to ensure you have the latest version of everything. Confirm you are using the latest version of Cesium, .NET 6 SDK, and Xcode. for UE. As well, please make sure all these elements are compiled into your project (confirm it’s listed into your .uplugin file).
After that, if the issue persists, to isolate the cause, test packing without Cesium included.