Packaging error - help asap

Hi, I am having problems to package my project. I managed to fix almost everything with finding errors, missing files etc. except this:

008UE4Editor-Cmd: [2015.09.16-11.02.30:158][  0]LogUObjectGlobals:Warning: Failed to find object 'Class /Engine/Tutorial/Mobile/SettingUpAndroidTutorial.SettingUpAndroidTutorial_C'
008UE4Editor-Cmd: [2015.09.16-11.02.30:750][  0]LogLinker:Warning: Asset '../../../Engine/Plugins/Runtime/LeapMotionController/Content/LM_PassthroughMaterial.uasset' has been saved with empty engine version. The asset will be loaded but may be incompatible.
008UE4Editor-Cmd: [2015.09.16-11.02.31:447][  0]LogCook:Display: Done creating registry. It took  0.53s.
008UE4Editor-Cmd: [2015.09.16-11.02.33:948][  0]LogUObjectGlobals:Warning: Failed to find object 'Object /Engine/Tutorial/SubEditors/PersonaAnimEditorTutorial.PersonaAnimEditorTutorial_C'
008UE4Editor-Cmd: [2015.09.16-11.02.34:010][  0]LogUObjectGlobals:Warning: Failed to find object 'Object /Engine/Tutorial/Mobile/SettingUpAndroidTutorial.SettingUpAndroidTutorial_C'

I dont know if this is the main problem… and whatever I do it fails…

Please help me fixing this problem because I have lost too much time over this with zero results.
:[1][1] [2][2]

58833-cook-2015.09.16-14.08.04.txt (972 KB)
[2]: 58834-uat_log.txt (590 KB)

PS: When I try to package a new project/Template it works without problems.

Hey NasteX,

I have looked into this issue further and have found that it was already reported in . UE-20906 is set as a major bug in the engine and we’re expecting it to be resolved in 4.10. Please keep in mind that this bug is not fixed yet, it’s still unresolved so I cannot guarantee it’ll be within 4.10, that’s simply what the timeline says at this time.

Please let me know if you have any further questions, thanks!

Thanks for the answer. Is there any possibility to have workarounds to this? I need to have the project packed for performance tests.

Anyone?.

I really need to know if there is some workarounds to this problem…

Currently there are no additional updates for this bug, including a work around. This bug is set as a level 2, major bug and it’s on our to do list. It’s still unresolved but we’re hoping to have this implemented soon.

Thanks!

I understand, thanks for answer. :slight_smile: