Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
5
Found in [Package]
2.0.3
Issue ID
ADDR-3548
Regression
No
ODR files from the local path are not loaded when using Addressables
How to reproduce:
1. Open the attached “addressablesLoad.zip” project
2. Open the “ResourceManagerConfig.cs” file
3. Observe the “ShouldPathUseWebRequest“ function
Expected result: Path is not treated as a web request
Actual result: Path is treated as a web request because function return is “return path != null && path.Contains(“://“)
Reproducible with: 1.19.19 (2021.3.31f1), 1.21.18f1 (2021.3.31f1, 2022.3.12f1), 2.0.3 (2023.1.18f1, 2023.2.0b15, 2023.3.0a11)
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Comments (1)
-
jaros_unity
Oct 31, 2023 07:42
please, fix it also in package for editor 2022.3.12f1, thank you
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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 (2.0.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.