Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a21
Issue ID
UUM-40842
Regression
No
Compilation error "CS2001" when spaces are entered into double-quoted path names in ".rsp" files
How to reproduce:
1. Open the attached user project “ResponseFileWithQuoteIssue.zip“
Expected result: No errors in the Console
Actual result: “error CS2001: Source file '…/ResponseFileWithQuotesIssue/bar.txt' could not be found.“ error in the Console
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a21
Reproduced on: macOS 13.4 (Intel), Windows 10 (by reporter)
Note: Might need to Enter Play Mode for the error to appear
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
- Line Brush blue outline appears at incorrect position when painting start of line in Tile Palette
- [URP] All materials render black when building via batchmode or without rendering Scene/Game view in Editor if Decal renderer Technique is set to "Automatic"
- Player Tags list shows extra blank space behind the scrollbar in the "Player Tags" settings window
- Edit Angular Limits gizmo handles are small and easy to miss-click in the Scene view
- Duplicate Player Tag save fails silently with no error or validation message
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
We expect this bug to be solved with our future work. And for now don't have space in the file name to unblock.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
We expect this bug to be solved with our future work. And for now don't have space in the file name to unblock.