I have a single React-Native app with a built-in calling feature. Right now, when a notification arrives and the app is in the foreground everything works, but if the app is in the background—or worse, killed—tapping the notification no longer routes the user to the correct “calling” screen on either iOS or Android. What I need • One seamless navigation flow that works automatically from every app state: foreground, background, and fully killed. • Support for both remote push notifications (FCM/APNS) and local in-app notifications that the calling module might raise. • Automatic deep-link style routing straight to the relevant screen the moment the user taps the notification—no interim prompts or previews. Current stack highlights react-native 0.71, react-navigation 6, Firebase Cloud Messaging, and CallKeep. If you prefer another proven library for handling headless/terminated-state notifications on either platform, I’m open as long as it doesn’t disrupt existing functionality. Acceptance criteria 1. Tapping any incoming call or message notification launches or brings the app to the foreground and lands on the target screen on both platforms. 2. Behaviour is identical after a clean kill (swipe-away) as in a normal background state. 3. No regression in existing call audio or PushKit functionality. 4. Clean, commented code or PR detailing the changes so I can merge confidently. If you’ve already handled deep-link navigation from cold starts in a React-Native project, you’ll find this straightforward. Let me know your estimated timeline and any clarifying questions.