Search Issue Tracker
By Design
Votes
0
Found in
2017.4.30f1
2019.3.0f4
Issue ID
1214025
Regression
Yes
[Scripting][Mac] Script throws NullReference errors on OnEnable() though object should be initialized on Awake()
To reproduce:
-Create a new unity project
-Import the attached script or copy from below (Project Window -> Import new asset)
-Create a new game object (GameObject -> Create Empty)
-With the new gameobject selected drag the script from the project window into the inspector
-Press play
Expected result:
No errors in the console
Actual result:
Error in console: "Object reference not set to an instance of an object"
Platforms affected:
Mac
Platforms unaffected:
Windows
Versions affected:
2017.4.30f1, 2018.4.12f1, 2019.3.0f5, 2019.0f4, 2020.1.0a19
The Script contents:
"using UnityEngine;
using Object = System.Object;
[ExecuteInEditMode]
public class ThisShouldntHappen : MonoBehaviour
{
private Object foo;
private void Awake()
{
foo = new Object();
}
private void OnEnable()
{
Debug.Log(foo.ToString());
}
}"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
Resolution Note:
The reason that this is happening, is because of the lifecycle of MonoBehaviour with ExecuteInEditMode.
For EditMode:
Awake is called when the Scene is active, awake will not be called again, before OnDestroy is called. That happens if unloading the Scene.
OnEnable is called after a domain reload.
In this scenario, the reason for the NullReference is that Awake has already been called, then if a domain reload happens "object" will be null because its not serialized. If the field is of a serializable type, and have the serializablefield attribute, it would not give this error.
Looking trough the documentation, we do not cover this area at all. I have pinged the documentation team so they will pick it up.