Search Issue Tracker
Won't Fix
Won't Fix in 1.20.X
Votes
0
Found in [Package]
1.19.18
1.19.19
1.20.0
1.20.3
1.20.5
Issue ID
ADDR-2986
Regression
No
Document why Addressables.UpdateCatalogs returns Success when the server is disabled
Steps to reproduce:
1. Open the user’s attached project
2. Open Assets/Scenes/SampleScene.unity
3. Open Window > Asset Management > Addressables > Groups
4. Press Build > New Build > Default Build Script
5. Open Window > Asset Management > Addressables > Hosting
6. Enable the “Local Hosting 0” server
7. Enter Play Mode
8. Press the “CheckForCatalogUpdates“ button
9. Press the “UpdateCatalogs“ button
10. “updateCatalog status: Succeeded“ message appears in the Console window
11. Disable the “Local Hosting 0” server
12. Press the “UpdateCatalogs“ button and observe the Console window
Expected result: A message appears in the Console window indicating that the update failed
Actual result: “updateCatalog status: Succeeded“ message appears in the Console window even though the server is disabled
Reproducible with: 1.19.18 (2020.3.39f1), 1.19.19 (2021.3.9f1), 1.20.0 (2022.1.14f1), 1.20.3 (2022.2.0b7), 1.20.5 (2023.1.0a8)
Reproducible on: Windows 10
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (1.20.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.