iOS Failed to find /Game/Maps/MyEntry after migrating content

Development Platform & Builds Mobile
, , , ,
1

I’ve been having trouble getting a project to run on iOS.

I’ve created a fresh project, with a new default map named it MyEntry.
I packaged and launched this on device just fine.

I then loaded up my other project, and migrated a single map into the new fresh project.
Changed no settings.
Attempted to package and launch, and I get a pop-up with the above error.

2

Attaching the log from the device [link text][1] maybe useful?
[1]: 100543-afsoc2.log (24 KB)

3

Hi BobWhite,

Please try these troubleshooting steps:

  1. In the ContentBrowser, right-click the Contents folder and select “Fix up redirectors in folder”
  2. In the Build Button on the Tools menu, click down arrow and choose “Map Check” -see if there are any errors regarding the new map (ie, missing assets etc.) Do this step specifically for the Main map and the new map you’ve migrated to the project.
  3. If the new migrated map is the initially loaded map, make sure this is set up correctly in the Project Settings
  4. In the Project folder, delete the Intermediate and Saved folders
  5. Save all
  6. Try to package
  7. If package fails, in the Project folder delete the Config folder (This will result in you having to re-enter your custom Project and Editor settings, however.)
  8. Try to package again.

If it still fails, please post the new output log.

Thanks,

.

4

So an update on this. I ran a fix-up redirects on the entire content folder, and attempted another build.
This time MyEntry could be found, but I continue to get errors pointing at other missing assets.
Specically Can’t find file ‘/Engine/MobileResources/HUD/DefaultVirtualJoysticks’

5

Did you run a ‘Map Check’ on the Newly Migrated map:

  1. Double-Click to Open (‘MyEntry’?) Map
  2. Run Map check
  3. Fix any errors from the Map Check
  4. Make sure you have the proper Game Mode, Default Pawn class etc. set up in World Settings.
  5. If the map in question is the default-starting map Make sure this is set up in the Project settings.
  6. Before packaging, PIE (Stand alone game) and check for errors. Correct these before packaging.

If it continues to fail, post the entire output log.

6

The fix up redirects did help a bit.
I walked through all the maps in the project and fixed any error that popped up.

Running in the app in the mobile preview isn’t throwing any errors and seems to work completely.
I also went through and deleted all of the engine generated folders, build intermediate, binaries, saved etc… to force a complete full-rebuild.

However after re-packaging I’m getting a lot of maps can’t be streamed in because the package can’t be found.link text

7

Are you using the Launcher version of the Engine or are you Compiling a source version with XCode? -If using Source, I recommend rebuilding the engine to solve missing module issues.

8

I’ve been compiling my own from source.

I finally had a breakthrough last night, it turns out some of the audio files in the project were built as 4 channel surround. These were causing the cooker to crash, however the automation tool wrongly assumed that the crash was just the cooker finishing up it’s job and so it moved along to packaging without actually saying anything.

Because nothing mentioned a crash in any of the packaging logs, (Instead it would log a warning from a physx module) I never actually went and looked into the Crashes folder, so all the logs appeared clean. Luckily (ha!) I had a different crash I was trying to hunt down, noticed the couple hundred entries in the crashes folder and started digging into those logs.

Granted my project is still having issues running, but at least all the assets are making it on the device.

9

So it turns out my problem was a few assets that were crashing the cooker for various reasons.
Sadly the automation tool never reported these as crashes, and instead would continue along happily packaging up an incomplete game.

The major culprits were some audio files that had 4 channels, and a landscape component that was convinced that a material existed in another map.

10

Thanks for posting your Answer. I’ll add “check crash folder” as a troubleshooting step for trickier ones like this. Just for clarification on my end, would you mind posting the log from the crash folder that shows the cooker crashing?

11

Sure thing.link text