Search Issue Tracker
Fixed in 2017.1.X
Votes
7
Found in
5.6.0f3
Issue ID
904415
Regression
Yes
Coroutines stop working if you create a GameObject in the runtime, set its parent and attach any UI component to it
To reproduce:
1. Open the project, attached by user (CoroutineBug.zip)
2. Open "scene" scene if not open
3. Press Play
4. Observe text fade in and fade out
5. Press Bug button in the game
6. Observe text stop fading
Expected: coroutine works without stopping if new game object was created at runtime, added as a child to another game object and any UI component was added to to the new game object
Actual: creating a new game object at runtime, adding it as a child to another game object and adding any UI component to the new game object stops coroutine
Reproduced in 5.5.2p4, 5.5.3p1, 5.6.0f3, 5.6.0p2, 2017.1.0b2
Did not reproduce in 5.5.0f3, 5.5.1f1, 5.5.2f1, 5.5.2p1
Regression introduced in 5.5.2p4
Fixed in 2017.1.0b8
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
- [iOS] Back Triple Camera is not focusing manually and automatically
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
skullthug
Aug 24, 2017 06:46
Bring this fix to 5.6 ffs!
skullthug
Aug 24, 2017 06:46
Bring this fix to 5.6 ffs!
NForest
Jul 24, 2017 16:47
this issue fixed in 5.6.2 ?
how to reproduce this issue? i can't download CoroutineBug.zip,,
moldywarpe
Jul 03, 2017 01:41
So this is now "fixed" in a beta release but not in a released version - that to me is NOT a fix!
Please apply this fix to 5.6 thanks.
jakeuj
Jun 27, 2017 10:59
Will 5.6 next version fix it?
Suhrahj
May 27, 2017 11:46
Very nice that we gotta wait for Unity 2017 for this fix.