Copyright © 2026 Unity Technologies
We haven't been able to reproduce this issue on any recent version of Unity, it is possible that the problem was addressed through other fixes/improvements in this area.
Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.
Reproduction steps:
1. Open the attached project "OculusGLES3RenderingBugs"
2. Open Build Settings Edit > Build Settings
3. Tick Development Build
4. Build And Run on a Quest 2 device
5. Go to Window > Analytics > Profiler
6. Try to connect the Profiler by selecting the Quest 2 device from the drop-down
Expected result: Profiler connects to the device
Actual result: Profiler fails to connect and returns an error in the Console window “Failed to connect. Check if there is an app running on the correct device and it was built with Developer Mode enabled. In case of further issues you can enable the player connection diagnostic switch to get more information“
Reproducible with: 2022.2.9f1, 2023.1.0b5
Not reproducible with: 2020.3.46f1, 2021.3.20f1, 2023.2.0a4
Reproducible with devices:
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Reproducible on: Windows 10 Enterprise 21H2
Notes:
Issues you vote on will appear here