`<view>` GameObject is not removed after Restart about core HOT 6 CLOSED

Applied the workaround in 0.15.2. This is still a bug in React side. But shouldn't be a problem in ReactUnity anymore.

from core.

The same <view> component is part of Canvas

from core.

Unity doesn't have a way to create objects but not place them in the scene. Ideally, we could place all newly created objects in [Offscreen], but I guess that would affect performance just by changing an object's parent. Alternative way would be to remove every object individually after canvas is destroyed, but that would also cost performance.

In an ideal case, there shouldn't be an error in the React rendering. So I don't want to implement this in a way that would affect performance much.

from core.

Unity doesn't have a way to create objects but not place them in the scene.

I believe you are correct in saying this, but can't you disable the objects to "fake" them not being there?

Alternative way would be to remove every object individually after canvas is destroyed, but that would also cost performance.

It might depend on how the canvas is destroyed, but if views are children of a specific canvas and you remove the canvas, I would expect it to remove the children as well, even if it would affect performance or not, because it needs to clean up after itself.

from core.

@Thundernerd Thanks for your suggestions.

Normally, when a view is created it is placed under the canvas. But in this case, an error happens before they are placed under the canvas. That is the root cause of this issue. So your second suggestion would not work.

Disabling and enabling objects can affect performance, even if it would be minor. Also objects would still be there, so I don't think that is a solution as well.

I have some plans to fix this, but haven't started working on it yet.

from core.

I misunderstood the issue first. I can see the issue after trying it again.

It may be caused by a bug in React. I reported it here: facebook/react#26518

Let's see what React devs say about it. If it doesn't get fixed in React, I will fix it with a workaround in ReactUnity.

from core.