IOS packaging fail

Development Platform & Builds Mobile
, , ,
1

After following all the instructions to get my game deployed to an IOS device - I am having problems packaging the project.
The following Errors appear in the Log:

[2014.10.30-14.45.26:214][ 92]LogPlayLevel:Display: Program.Main: ERROR: Command failed (Result:1): C:\Unreal Engine\Unreal Engine 4.4.0\Unreal Engine\Engine\Binaries\DotNET\IOS\IPhonePackager.exe RepackageFromStage “Engine” -config Development -sign -stagedir “C:\Users\User\Documents\Unreal Projects\Heist 4.4\Saved\StagedBuilds\IOS” -project “C:\Users\User\Documents\Unreal Projects\Heist 4.4\Heist.uproject”. See logfile for details: ‘IPhonePackager.txt’

[2014.10.30-14.45.26:215][ 92]LogPlayLevel:Display: ProcessManager.KillAll: Trying to kill 0 spawned processes.

[2014.10.30-14.45.26:512][ 99]LogPlayLevel:Display: Program.Main: AutomationTool exiting with ExitCode=1

[2014.10.30-14.45.26:512][ 99]LogPlayLevel:Display: Domain_ProcessExit

[2014.10.30-14.45.26:515][ 99]LogPlayLevel:Display: ProcessManager.KillAll: Trying to kill 0 spawned processes.

[2014.10.30-14.45.26:526][ 99]LogPlayLevel:Display: AutomationToolLauncher exiting with ExitCode=1

[2014.10.30-14.45.26:526][ 99]LogPlayLevel:Display: copying UAT log files…

[2014.10.30-14.45.26:526][ 99]LogPlayLevel:Display: RunUAT.bat ERROR: AutomationTool was unable to run successfully.

[2014.10.30-14.45.26:631][102]LogPlayLevel:Display: BUILD FAILED

If anyone could help then that would be great! I saw somewhere that the engine needed re-building in ‘Development’ rather than ‘Development Editor’ - I have done this but still no luck.

2

Anyone know what could be causing this?

3

It says something about “missing UE4game.stub” if that helps any

4

Anybody? Still no luck sorting this

5

Hi whirlpoole,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, could you please submit a new report for it.