-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openURL() not respecting deep links / universal links #38266
Comments
|
|
This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days. |
This issue was closed because the author hasn't provided the requested feedback after 7 days. |
Hi @Estevete, do you have any solution for this? I also have the same issue. |
Hi. Not really. A possible workaround could be checking wether you're on mobile. If you are on mobile, then parse the URL to the app scheme and check with canOpenUrl. If canOpenUrl is false, then keep using the URL, otherwise open the app scheme (since it means you have the app installed). But TBH, I think this feature is quite commonly used and there's no info about it on the docs... |
Facing the same problem, I managed to open a hidden webview and open the universal links inside the webview. |
Description
I have configured deep links & Universal Linking in my app (AASA, Assetlinks...). Let's say my Universal Link is https://example.com/profile. If I tap on that link outside the app, it opens correctly the app.
The issue comes when I use
Linking.openURL("https://example.com/profile")
inside the app. It opens the WebBrowser instead of opening in the app (since it's a universal link).If I try to open for example instagram
openURL("https://instagram.com")
, it opens the instagram app (and not the web browser)...The reason of this is because I have implemented the redirectURL, so if I send any link through the email and the user has to be logged in in order to access to it, then I redirect the user after he logs in.
Some months ago, this used to work correctly. This is happening on Android and iOS.
The same behavior happens if I use
expo-linking
package instead.React Native Version
0.71.8
Output of
npx react-native info
Steps to reproduce
The text was updated successfully, but these errors were encountered: