0
Fixed (Unreleased)

object at index 0 is null AND Object reference not set to an instance

Mark McCorkle 3 months ago updated 3 months ago 3


I've done some digging on what causes this and the best I can find is that these errors are due to out of order loading of game objects (and serialized objects) in the inspector window.

The official fix is: Close and re-open your inspector.

But when I'm running Peek, that doesn't work because (I assume) Peek keeps a copy of the inspector window loaded and hidden somewhere. 

Is there a way to get peek to "close and reopen" its reference to the inspector window?  

I am happy to share the collab project if that helps you reproduce / debug.  


Unity Version:
2018.4.13f1
Peek Version:
1.1.6
+1
Need More Information

Hi Mark,

Thank you for the bug report and sorry about the issue.

I thought I had fixed it but we did see it come back even on our team recently.

The cause is unclear for us. In your project, can you reproduce it consistently?

If we can't reproduce, we could attempt fixes but we'd never know if they actually work, so it's be a very tedious process over multiple versions.

In the mean time, I know restarting the Unity editor fixes the issue.

+1
Fixed (Unreleased)

Hi Mark,

I investigated the issue further and I was able to isolate and fix it. It will be fixed in the next release.

That's awesome!  Sorry I hadn't been able to get back on this during the week -- but I'm glad you were able to reproduce.  

I will work on reproducing my other bug (the missing script one) tomorrow for you.  Thank you for taking a look into it.