Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3
2019.3.13f1
2020.1
2020.2
Issue ID
1253630
Regression
No
Instantiating UI GameObjects from an Asset Bundle with WeakReference results in errors
How to reproduce:
1. Open submitted project (WeakReferenceTest.zip)
2. Open the Test Scene
3. Enter Play Mode
4. Click the 'test WeakReference' button
Expected result: no warnings or errors are thrown in the Console window
Actual result: multiple warnings and errors are thrown in the Console window
Reproducible with: 2018.4.23f1, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Resolution Note:
Unity currently does not support the use of weak references with loaded assets. We may add support for this usage in the future, but please avoid it for the time being.