Android Manifest Bug, Prevents launching on device

anonymous_user_b53ccd481
Mon, 23 Jul 2018 16:13:48 +0000
Mobile

I have found an unusual Bug when launching to Android found in both 4.19 and 4.20 and I was wondering if anyone has seen it before.

The bug is caused because the Manifest_UFSFiles_android.txt************* file is written incorrectly.

i.e. this line gets wrote

/GearVRControllerMaterial.uasset 2018-07-20T20:43:10.000Z

instead of

Engine/Plugins/Runtime/Oculus/OculusVR/Content/Meshes/GearVRControllerMaterial.uasset 2018-07-20T20:43:10.000Z

I believe this is caused by the localisation toolkit due to localisation being mixed up after this but I have yet to replicate in new project

this is error when trying to launch

Running: C:\NVPACK\android-sdk-windows\platform-tools\adb.exe -s M2HDU18310002543  pull /sdcard/UE4Game/AdvancedVehicleKit/Manifest_NonUFSFiles_Android.txt "D:\Racing-Game\Saved\StagedBuilds\Android_ASTC\Manifest_NonUFSFiles_Android.txt_M2HDU18310002543"
LogPlayLevel: Took 0.050954s to run adb.exe, ExitCode=0
LogPlayLevel:

ERROR: System.ArgumentException: Attempt to construct staged filesystem reference from absolute path (/GearVRControllerMaterial.uasset). Staged paths are always relative to the staging root.
LogPlayLevel:           at StagedFileSystemReference..ctor(String InName)

This only occurred on Android 8+ devices.

Log file here LogPlatformFile: Not using cached read wrapperLogInit: Display: RandInit(-7772 - Pastebin.com

Link to manifest file here Manifest_UFSFiles_Android.txt_M2HDU18310002543 - Google Drive

If anyone has seen this before I would love to know a solution

Thank you

11 posts - 1 participant