Search Issue Tracker
Won't Fix
Won't Fix in 1.21.X
Votes
0
Found in [Package]
1.21.15
1.21.17
Issue ID
ADDR-3502
Regression
No
Error when loading remote content with usernames containing ".hash"
Reproduction steps:
1. Create a new user for your os that has “.hash“ in the name
2. Open the attached project “ErrorRepro“
3. Enter the Play mode
Expected result: No errors in the console
Actual result: File path denied warning or missing path error with “.hash“ changed to “.json“
Reproducible with: 1.21.15 (2021.3.29f1, 2022.3.8f1, 2023.1.10f, 2023.2.0b6), 1.21.17 (2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6)
Reproducible on: Windows 10
Not reproducible on: no other environment tested
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.21.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.