Meta Quest 2 Stuck on Loading Screen on Android Build - UE 5.4

I’m attempting to build an Unreal Engine 5.4 Project on a Meta Quest 2 (Windows OS, Intel Iris Xe GPU) starting from the default VR template. While the ADB commands successfully install the app, the app is stuck on a black loading screen (three dots under UE logo). I attempted this for both “Development” and “DebugGame” under Android (ASTC) without success.

My project consists simply of the VR Template and MetaXR Plugin (Version 1.103.0).

For Platform - Android settings, I have target and minimum SDK versions of 32.

I have “Support Vulkan” checked. OpenGL ES 3.2 is not supported. Under Meta XR Plugin settings, I have “XR API” set to “Oculus OVRPlugin + OpenXR backend”

My computer does not meet minimum hardware specs for Quest Link (Intel Iris Xe Graphics) so I am trying to sideload the installation using these commands from the ASTC directory:

adb devices
adb uninstall com.YourCompany.[AppName]
adb install [AppName]-arm64.apk
adb push main.1.com.YourCompany.[AppName].obb /sdcard/Android/obb/com.YourCompany.[AppName]

On Android Studio SDK Manager I have the following installations:

I have been able to do this before with a VR Template, but I’m not sure what caused it to be fixed back then and I’m unable to replicate the same success.

I think my issue is similar to these two threads, but it doesn’t seem like the suggestions there seem to fix my situation. However, I do not have a Steam VR nor OpenXR Unreal plugin so not sure if that’s the issue although my build worked in the past without either.

How do I get the installation to get past the infinite loading screen? I’m inexperienced with VR dev, so unfortunately I have no clue how to debug a situation like this.

hello. I have the same problem. i have built the same project over and over for months now and no issues in the quest 2. all of a sudden i built it with the same exact settings and now it just gets stuck in the loading screen. no idea why its happening. Even tried the default VR template that has also built successfully in the past and still the same issue. leads me to believe that meta has made a change to the settings either purposely or accidentally and it has caused issues. Pls if you find a fix pls share on this chat

hello again. i think i found a solution if you eventually come back to this post, i solved the issue by packaging the build on my pc before installing it into the quest 2 through the batch file installer. i hope that helps