Add getLaunchDeepLink for cold start deep links - #138
Merged
Merged
Conversation
rlepinski
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Adds a one-shot
getLaunchDeepLink()to both platforms that returns the deep link from the notification tap that launched the app, or null once the launch resolves without one. Also fixes FeatureTests compiling against iOS SDK 20.Why are these changes necessary?
React Navigation's declarative linking asks for the launch URL once at mount, and our deep link event lands too late on cold start, so apps open to the default route.
How did you verify these changes?
New tracker unit tests on both platforms, full iOS scheme tests and
testDebugUnitTestgreen.