Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
Issue ID
1202584
Regression
No
ScriptUpdater does not work for users with spaces/invalid characters in their User Names
Reproduction steps:
1. Log in as a user that contains spaces in the name
2. Create a New Project
3. Import the "Trigger.cs" script
4. Check the Editor log to see if the "ScriptUpdater.exe" has run
5. Check if the "ScriptUpdater.exe" path that follows the value "Unity[^\\]+\.dll$" is in quotes
6. Check if the "Trigger.cs" script got updated
Expected Result: ScriptUpdater works for users with spaces/invalid characters in their User Names
Actual Result: ScriptUpdater does not work for users with spaces/invalid characters in their User Names
Reproduced with: 2020.1.0a16, 2019.3.0f3, 2019.2.17f1, 2018.4.15f1, 2017.4.35f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
Add comment