You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with Expo SDK 50 and Expo Router version 3.
For my marketing campaigns, I'm using a deep linking feature provided by Adjust (https://help.adjust.com/en/article/deep-links).
The deeplinks from Adjust have the format q***.adj.st.
Problem
I need to convert the Adjust deeplink before I can use it to navigate to the appropriate screen within my app.
However, with the introduction of Expo Router, I no longer have direct access to the linking prop of the NavigationContainer and to the methods getInitialURL and subscribe.
I've tried using Linking.useURL(), but I can't intercept the incoming deep link before it's processed and the app navigates to the targeted screen.
Question
How can I access the linking configuration to use customs getInitialURL and subscribe with Expo Router without having to patch node_modules/expo-router/build/link/linking.js?
The text was updated successfully, but these errors were encountered:
Context
I'm working with Expo SDK 50 and Expo Router version 3.
For my marketing campaigns, I'm using a deep linking feature provided by Adjust (https://help.adjust.com/en/article/deep-links).
The deeplinks from Adjust have the format
q***.adj.st
.Problem
I need to convert the Adjust deeplink before I can use it to navigate to the appropriate screen within my app.
However, with the introduction of Expo Router, I no longer have direct access to the
linking
prop of theNavigationContainer
and to the methodsgetInitialURL
andsubscribe
.I've tried using
Linking.useURL()
, but I can't intercept the incoming deep link before it's processed and the app navigates to the targeted screen.Question
How can I access the
linking
configuration to use customsgetInitialURL
andsubscribe
with Expo Router without having to patchnode_modules/expo-router/build/link/linking.js
?The text was updated successfully, but these errors were encountered: