Unity Build nullReference, but editor sees through it!

Questions & Answers
1

Hi there, sorry to bother but this kind of errors are new to me because I’ve been coding mainly inside the editor!

It seems that 1 line in my Awake() returns != null when in editor, and == null once built.

This is the line, though it doesn’t help too much per se:

		//Outputting
		textBehaviour.LinesToPrint(myDialogue.NpcLines[0]);

textBehaviour is an instance of one of my Classes, it just has to print a string.

I believe that, since the development build says nullReference and not Index out of Range, the problem is that instance itself.

Could it be that myDialogue has something to do with this too? That maybe the error derives from a null parameter?

In the editor I did tweaked scripts execution order to fit my needs… maybe in builds that’s a bad thing?

I’m trying to build for mac.
I know I’ve provided scarce infos on this, but I don’t know what to look for… I could really use some help.

I’ve looked previous similar questions but I can’t understand how it’s possible that the same variable works if in editor and screws up if in build!

Thanks :smiley:

2

What is null?

textBehaviour or myDialogue?

If you can’t tell, figure it out. Attach a debugger or call print or Debug.Log/Warning/Error.

void Awake()
{
    LogNullError(textBehaviour, "textBehaviour");
    LogNullError(myDialogue, "myDialogue");
    textBehaviour.LinesToPrint(myDialogue.NpcLines[0]);
}

void LogNullError(object o, string name)
{
    if (o == null)
        Debug.LogErrorFormat(this, "The variable {0} is null", name);
}

Then figure out where that object is set. Maybe it’s a result from a file load? Maybe that part behave different depending on the location of your executable or operating system? And so on.