Unreal 5.4.4 Fork Deployment issues

Unreal Engine
1

Magic Leap SDK version: 1.9.0 (plugin: 1.6.0)
Unreal Engine version: 5.4.4 from Source
ML2 OS version: 1.9.0
MSVC v143 - VS 2022 C++ x64/x86 build tools (14.38-17.8)

I'm unable to deploy to the device. The project compiles successfully, but when it goes to deploy it gives this error:

LogPlayLevel: UAT: Running: C:\Users[name]\AppData\Local\Android\Sdk\platform-tools\adb.exe -s G862XT00004B install -r "G:\Perforce\Magic_Leap\AR_Demo 5.4 - 2\Binaries/Android\AR_Demo-arm64.apk"
LogPlayLevel: UAT: adb: failed to install G:\Perforce\Magic_Leap\AR_Demo 5.4 - 2\Binaries/Android\AR_Demo-arm64.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
LogPlayLevel: UAT: Performing Streamed Install
LogPlayLevel: UAT: Took 1.38s to run adb.exe, ExitCode=1

I think this may have to do with my inability to disable "Support arm64" and enable "Support x86_64"?

3

image
image762Ɨ377 21.4 KB

need to be NOT arm64

2 Likes
4

Hey @jdeboer

I think your suspicion is correct in that you are failing to deploy your app due to target architecture mismatch.

Are you saying that for this specific project, you cannot disable the Support arm64 option due to a dependency or something similar?

In order to deploy an app to the ML2 device, you must enable Support x86_64 and disable Support arm64.

I'm not sure if it will work, but you could try enabling both options and deploying to the ML2 device, although this will most likely end up with undesired behavior in your app.

1 Like
5

The options are greyed out. Iā€™m unable to change any of the build options, including unchecking the currently selected options.

image
image1330Ɨ430 13.2 KB

6

I believe I solved it. I had started that particular project using the VR template. When starting a blank project following the Getting Started thread, those options are enabled. Thank you for talking it through with me. It lead me in the right direction.

2 Likes
7

Yeah it could have been a different project setting in the VR template that wouldn't allow you to change the target architecture.

Glad to hear you resolved it though!