Inside the AddComponet function, GameoObject temporarily becomes Disable.

Hey there,

I tried opening my project with Unity 5.6.0 f1.
However, it did not work properly.
The cause was that the coroutines had stopped.
I looked for the cause of coroutines stopping.
StopCotouine etc are not called.
The cause was to make the object Disable at unintended timing.
It is called at the time of AddComponet.
Strangely enough, that AddComponet is calling for another object.

This is the stack Torres of Debug.log.


Immediately inside Disable, it is set to Enable inside AddComponent.
As a result, the active state returns to its original state, but in this way the coroutine stops. It is not good to be called at an unintended timing.

I tried to reproduce it by making a simple project, but it does not reproduce.
There seems to be some condition.
It did not happen until Unity 5.5.2.

 

Hello. Thank you for your reply.
My bug reports are (Case 892530) and (Case 892500).
The coroutines are stopped by calling OnDisable.

I was replied as a known problem.
Https://issuetracker.unity3d.com/is...nt-to-game-object-in-play-mode-via-the-script

I hope that the problem will be resolved by the official release of Unity 5.6.
Since it affects all the components of the hierarchy, I think that the problem will frequently occur.
If such a change can not be avoided, please let me know by Warning or Error.
Now I have a hard time finding out when the coroutines have stopped.