Not sure what I did to cause this error but it’s popping up now whenever I enter playmode. By the sounds of it there might be a localization component that is referencing a component that no longer exists with it. Is there a way for me to find it?
You could try putting a breakpoint into the callstack.
Looks like there is a GameObjectLocalizer trying to change an Image component. Can you file a bug report so we can look into this? We should detect if the object is destroyed earlier on.
Hey! Thanks for the suggestion on breakpoints. I found the GameObject that’s causing the error. Unfortunately, I’m still left confused. It says the Image component has been destroyed but it’s still there in the scene (attaching pictures of these) and I do not run any destroy methods on the object.
The GameObject in question:
The GameObject in scene:
It looks fine. Are you sure that’s the correct GameObject? Maybe it’s a different one?
What version of the package are you using? Can you try 1.3.2?
Based on the Scene path from the break point, that should be the right one. There is no duplicate / same hierarchy in the scene. The Localization version we are using is 1.3.2.
Sounds like a bug. Are you able to file a bug report and include the project so we can debug it?
Alright I have successfully filed the bug report. It’s listed as IN-16578.
1 Like
Could you please give me an URL to the issue, I can’t seem to find it on my own.
Is this issue related? Seems a bit different than what I am experiencing.
Yeah, like karl_jones said, this doesn’t seem related?
Sorry that’s the wrong bug. IN-16578 is still with QA and not on the issue tracker yet.
@Kogamma They have responded to the bug report and suggested setting the WaitForCompletion on the GameObjectLocalizer component to true. This has worked for me, so hopefully it works for you too.
1 Like