Search Issue Tracker
Fixed in 2017.1.X
Votes
2
Found in
5.6.1f1
Issue ID
914272
Regression
Yes
WWW coroutine breaks when adding UI component as a child via script
To reproduce:
1. Open project attached by the user
2. Open "Main" scene if not opened
3. Hit play and in console notice that first xml file was loaded successfully, then UI element was added to the ExhibitManager game object (as a child)
4. Notice that second xml file is not loaded
Expected: After adding UI element, second xml file is loaded (script "ExhibitManager.cs").
Actual: Loading coroutine breaks after UI element is added.
Regression introduced in: 5.6.0b8
Reproduced with : 5.6.0f1, 5.6.1f1, 2017.1.0b6, 2017.2.0a1
Not reproduced with : 5.5.0f3, 5.6.0b7
Note: UI element is being added via script. Adding it as a parent does not break anything.
Fixed in: 2017.2.0a2
Backported to: 5.6.2p2, 2017.1.0f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment