react-navigation / react-navigation/react-navigation
[Expo-Linking] Can't receive params when the application already opened.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 24.5k
- Forks
- 5.1k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 18
Description
Current Behavior
- When I closed the app it's open the screen and received the params, so when The app already opened it's can't receive any params.
Expected Behavior
- able to received the params when the app already opened.
How to reproduce
-
the example code in the navigation configure :
-
const linking = {
prefixes: [rootUrl],
config: appLinkConfigure,
};
with the appLinkConfigure is: -
const appLinkConfigure = {
screens: {
[MY_SCREEN_NAME]: {
path:${MY_PATH}/:slug,
parse: {
slug: (slug) =>${slug},
},
},
},
}; -
"@react-navigation/native": "5.7.2", "@react-navigation/stack": "5.8.0", "expo-linking": "~2.0.1".
Environment
- Expo SDK 40
| software | version |
|---|---|
| iOS or Android | |
| @react-navigation/native | |
| react-native | |
| expo | |
| node | |
| npm or yarn |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied linking configuration with Expo SDK 40 and the listed React Navigation versions, testing both cold-start and already-open states on iOS or Android. Trace how Expo-Linking and the navigation setup handle incoming links while the app is open. Done means the configured slug reaches the target screen in both states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100