Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0a17
Issue ID
621594
Regression
Yes
Can't connect MD debugger to standalone builds
-e: see title, ends with an error "could not connect to the debugger"
-issue reproduced for windows/osx/linux standalone
-repro:
--build windows standalone that has an actual script with Script Debugging enabled
--run build
--open MD
--try to attach to the standalone player
--NOTICE MD error and you are not connected to the player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warning icon is cut off and misplaced in Inspector when selecting a Shader with a compiler warning
- AI Navigation Sample Scenes do not work and throws “InvalidOperationException”, “Curl error3”, “CrashReporter”, and “NullReferenceException” errors when using the new Input System Package (default) on a new project
- Bottom of Build Size window in Project Auditor becomes inaccessible when a monitor has a high display scaling
- AI Assistant fails to load account information when AI assistant is opened
- [Linux] Improve "GPUResidentDrawer" warning message to include actionable guidance when creating a new Unity project using Universal 3D Template
Add comment