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.
Comments (1)
-
vincismurf
Aug 09, 2019 11:43
So are you talking to them about this?
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2018.2.X):
We're investigating this with Oculus. The fix would need to be on the Oculus side.