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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Resolution Note:
Use case error in Addressables-Sample code, updated in this PR https://github.com/Unity-Technologies/Addressables-Sample/pull/27