Search Issue Tracker

Fixed in Unity 2017.1



Found in


Issue ID




Coroutines stop working if you create a GameObject in the runtime, set its parent and attach any UI component to it




Priority: 2Necessary for shipping a final release


Severity: 3Workaround is possible

To reproduce:

1. Open the project, attached by user (
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

Comments (4)

  1. 863dbe02d6b625569199a2654b74937c?d=mm


    Jul 24, 2017 16:47

    this issue fixed in 5.6.2 ?
    how to reproduce this issue? i can't download,,

  2. 5491351c9b94c7cf2755bebfcca786b4?d=mm


    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.

  3. 174d622bd6535e33fcb774975065b826?d=mm


    Jun 27, 2017 10:59

    Will 5.6 next version fix it?

  4. De922a6d504ba43f0eb3d9b3cfd585ca?d=mm


    May 27, 2017 11:46

    Very nice that we gotta wait for Unity 2017 for this fix.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.