Skip to main content
Samueletesi21
New Participant
August 29, 2026
Question

Quest 2 standalone Unity OpenXR build launches to black screen while Quest Link Play Mode works

  • August 29, 2026
  • 0 replies
  • 26 views

Hi,

I'm having an issue with a Unity 6 application built for Meta Quest 2 using OpenXR. The project works correctly when I enter Play Mode in the Unity Editor and use the Quest 2 through Quest Link. In that case, the scene is rendered correctly and the application behaves as an immersive VR experience. However, when I use Build And Run and install the APK directly on the Quest 2, the application launches but I only see a black screen. My setup:

  • Meta Quest 2
  • Quest OS: Android 14 / API 34
  • Unity 6000.0.51f1
  • OpenXR Plugin 1.14.3
  • Android build
  • ARM64
  • IL2CPP
  • Vulkan
  • Development Build
  • Initialize XR on Startup enabled
  • OpenXR selected under XR Plug-in Management for Android

 

What I have already checked:

  • The same scene works correctly in Unity Editor Play Mode through Quest Link.
  • Changing the first scene in the Unity Build Scene List does not change the behavior.
  • I tried changing the Main Camera background to a solid red color, but the standalone build still shows black.
  • The application does not appear to crash.
  • adb logcat shows that OpenXR initializes successfully.
  • The OpenXR session reaches XR_SESSION_STATE_VISIBLE.
  • Vulkan initializes successfully.
  • I do not see any obvious Unity exceptions or fatal errors in the log.

I also tested the installed package with:

adb shell cmd package query-activities --brief -a android.intent.action.MAIN -c com.oculus.intent.category.VR -p com.Samuele.VRApp

and it returns:

No activities found

I'm not sure whether this is expected for a Unity 6 OpenXR application or whether it indicates that the APK is missing some Quest-specific manifest/configuration. At the moment I am using the standard Android build profile in Unity. Could this behavior be caused by:

  • a missing Meta Quest/OpenXR configuration;
  • an Android manifest issue;
  • the use of the standard Android build profile instead of a Quest-specific configuration;
  • a graphics/Vulkan compatibility issue;
  • or some other difference between Quest Link Play Mode and a standalone Quest build?

What would be the recommended checks for diagnosing a Quest 2 standalone build that reaches XR_SESSION_STATE_VISIBLE but renders only a black screen?

Thanks.

Terms & ConditionsAccessibility statement