Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.6.2
Issue ID
ADDR-1045
Regression
No
[Addressables] using ReleaseInstance() on ComponentReference<TComponent> reference does not destroy the Game Object
Reproduction steps:
1. Open the attached project in "ComponentReference.zip"
2. Enter Play Mode
3. Press and release 'a' button on the keyboard¹
Expected results: Prefabs instantiated by the "Spawner" will be destroyed
Actual results: prefab ColorChangeCube is not destroyed and remains in the Scene
Reproducible with Addressables 1.6.2 (2018.4.19f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2)
Could not test with 2017.4 because there is no Package Manager
*1. Sometimes more than one keypress and release is needed in newer Unity versions
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Use case error in Addressables-Sample code, updated in this PR https://github.com/Unity-Technologies/Addressables-Sample/pull/27