Search Issue Tracker
Won't Fix
Votes
4
Found in
2018.2.0b9
Issue ID
1059569
Regression
No
[android]Wait For Managed Debugger does not work with Oculus Go
Reproduction Steps:
- Set Android as build target
- Enable XR with Oculus SDK
- In build settings, check development build, script debugging, and wait for managed debugger
- Build and Run
Expected:
User is able to attach a managed debugger
Observed:
After launching the application a dialogue shows up, split across left and right eye (not stereoscopic), showing the text "Debug - You can now attach a managed debugger if you want" and an OK button. There is no way to dismiss the dialogue and you cannot attach the managed debugger.
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
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Resolution Note (2018.2.X):
We're investigating this with Oculus. The fix would need to be on the Oculus side.