MISSINGREFERENCEEXCEPTION: OBJECT HAS BEEN DESTROYED

What Is the Error?

Unlike a NullReferenceException (where a variable was never assigned anything in the first place), a MissingReferenceException occurs when a variable did point to a valid GameObject or Component, but that object was subsequently destroyed (via Destroy(gameObject) or a scene change) while another script continues trying to read its position, call its methods, or trigger its delegates.

Why Does It Happen?

• Lingering Event Listeners: An object subscribed to a static C# event, was destroyed, but forgot to unsubscribe in OnDisable().
• Follow Camera Targeting Destroyed Player: A follow camera or missile homing script reads target.position after the target aircraft has blown up and been destroyed.
• Coroutines Running on Dead Objects: A coroutine or Invoke() continues executing after the target has been removed from the scene.

Quick Fix

// ❌ BAD: Throws MissingReferenceException if target was destroyed!
void Update()
{
    transform.LookAt(target.position);
}

// ✅ CORRECT: Safe check accounts for destroyed Unity objects
void Update()
{
    if (target != null)
    {
        transform.LookAt(target.position);
    }
}

Step-by-Step Fix: Unsubscribing Event Listeners

The most frequent cause in production games is event delegates. Always pair event subscriptions in OnEnable() and OnDisable():

public class HealthBarUI : MonoBehaviour
{
    private void OnEnable()
    {
        PlayerCombat.OnHealthChanged += UpdateHealthBar;
    }

    private void OnDisable()
    {
        // ✅ CRITICAL: Unsubscribes before GameObject is destroyed or scene unloads!
        PlayerCombat.OnHealthChanged -= UpdateHealthBar;
    }

    private void UpdateHealthBar(float health, float max)
    {
        // UI updates here safely
    }
}

Related Guides & Tools