Due to serverSendObjectRemoval() being called twice for a single object, the console reports error since the object has already been destroyed. I have already implemented some redundancy to mitigate the errors by checking whether an object has been already destroyed prior to removing object, but this does not resolve the root cause of this issue.
Due to serverSendObjectRemoval() being called twice for a single object, the console reports error since the object has already been destroyed. I have already implemented some redundancy to mitigate the errors by checking whether an object has been already destroyed prior to removing object, but this does not resolve the root cause of this issue.
Steps to Reproduce the Problem
Screenshots
-->