Search Issue Tracker
Fixed
Fixed in 1.21.14
Votes
0
Found in [Package]
1.21.12
Issue ID
ADDR-3393
Regression
Yes
Sprites and other nested assets are not loaded correctly when using binary catalog
Reproduction steps:
1. Open the attached project “ReleaseIssueProject”
2. Open the Project Settings window (Edit > Project Settings)
3. In the Project Settings window select the “Player” tab
4. In the “Other Settings” tab make sure that “ENABLE_BINARY_CATALOG” is included in the “Scripting Define Symbols” field
5. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
6. In the Addressables Groups build the Addressables (Build > New Build > Default Build Script)
7. Make sure that the “Play Mode Script” is set to “Use Existing Build”
8. Open the “Assets/Scenes/SampleScene” scene
9. Enter the Play mode and then stop it
10. Inspect the Console window
Expected result: There are no messages in the Console window
Actual result: Multiple “Addressables.Release was called on an object that Addressables was not previously aware of. Thus nothing is being released” errors are printed in the Console window
Reproducible with: 1.21.3 (2020.3.48f1), 1.21.12 (2020.3.48f1, 2021.3.26f1, 2022.2.21f1, 2023.1.0b17, 2023.2.0a16)
Not reproducible with: 1.21.2 (2020.3.48f1)
Reproducible on: macOS 13.3 (Intel)
Note: If “ENABLE_BINARY_CATALOG” is not included when building the Addressables the errors doesn’t appear
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Add comment