Search Issue Tracker
Not Reproducible
Votes
2
Found in
2022.2.12f1
2023.2.0a7
2023.3.0a3
6000.0.0b11
7000.0.0a1
Issue ID
UUM-30720
Regression
Yes
[Oculus][Android] Unable to connect Profiler to a device when built with Development Build
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:
- It does not reproduce 100% of the time, and sometimes requires the Player to be restarted
- Could not find the first affected or the first fixed version due to the bug only reproducing sometimes and the results are not consistent
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Palette Settings link to the documentation isn’t working
- "Type Options" and "Node Library" dropdowns do not open when clicked on the title
- Public char variables uneditable in Inspector when project setting "Use IMGUI Default Inspector" is enabled
- IAP Listener component’s list titles go out of bounds when resizing the Inspector window horizontally
- Selected Camera sublayer blends with highlight color in Graphics Compositor window when Editor theme is set to Light
Resolution Note:
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.