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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Resolution Note (2018.2.X):
We're investigating this with Oculus. The fix would need to be on the Oculus side.