How to Handle Notification Taps in Expo Apps Across All Launch States

When a user taps a push notification, the app's entry point varies depending on whether it was terminated, backgrounded, or active at the time. Expo provides two separate mechanisms to cover these cases: getLastNotificationResponseAsync() for cold launches and addNotificationResponseReceivedListener() for background or foreground taps. Developers should avoid triggering navigation before authentication checks or the Navigator is fully ready, as this can cause routing conflicts. To prevent duplicate listeners during screen remounts or Fast Refresh, the listener subscription should be cleaned up with remove(). For security, externally provided URLs should be validated against allowed hosts and converted to internal routes before being passed to the router.