You notice your Angular component's ngOnDestroy method is not called when navigating away. What is the most likely cause?

medium📝 Debug Q14 of 15

Angular - Lifecycle Hooks

You notice your Angular component's ngOnDestroy method is not called when navigating away. What is the most likely cause?

AThe component is never destroyed because it is cached or reused

BYou forgot to implement <code>OnDestroy</code> interface

CYou used <code>ngOnDestroy</code> instead of <code>onDestroy</code>

DAngular does not call <code>ngOnDestroy</code> on navigation

Step-by-Step Solution

Solution:

Step 1: Understand when ngOnDestroy runs
ngOnDestroy runs when Angular destroys the component instance.
Step 2: Identify why it might not run on navigation
If the component is cached or reused (e.g., via route reuse strategy), it is not destroyed, so ngOnDestroy won't run.
Final Answer:
The component is never destroyed because it is cached or reused -> Option A
Quick Check:
ngOnDestroy runs only on actual destruction [OK]

Quick Trick: ngOnDestroy runs only if component is truly destroyed [OK]

Common Mistakes:

Master "Lifecycle Hooks" in Angular

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Angular Quizzes