![]()
While this message is annoying and we all looking forward to a fix, did anyone also bug-reported that the object name is actually missing in that message? ![]()
Fix was due to land in 6 or 7 AFAIK.
The last couple of betas were really light on fixes for some reason… ![]()
The changeset with the fix for this has been queued to be merged yesterday. It will most likely be in b9.
Thanks a lot Leonhard.
You’re welcome ![]()
Destroying object “” is not allowed at this time.
…in b9, it’s not fixed yet
Wouldn’t it be easier, for both sides, if the issue status shows the actual version number in which the fix will be available first. In this case, “Status: Fixed in Unity 5.6.0b10” for example.
The “Status: Fixed in …” message is otherwise rather pointless during the alpha/beta-cycle and causes even more confusion as various forum posts show.
@Adam-Mechtley pointed out in another thread it’ll be ready by beta 10 or at least one of the release candidates as the fix got bundled with another, bigger thing under review.