-
Notifications
You must be signed in to change notification settings - Fork 13
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
[iOS] Deeplink info not surviving after going through Apple App Store #24
Comments
+1 |
Same issue, android works fine, on ios after clicking the dynamic link and downloading app through app store and opening the app - deeplink params are missing. Something must've changed on apple side |
@FeN1x1 removing the https from the my dynamic link domain in the applinks under associated domain fixed my issue |
@sajath-45 unfortunately I'm already using the |
@FeN1x1 can you show we what value have you specified for applinks: |
Hey guys, sorry for the late response to this. I actually can't reproduce this at all for my apps on my iPad with iOS 16. I follow these steps:
Can you provide some more information about what parameter you pass to the link? |
I've managed to fix the problem - capacitor/vue project where Storage api caused weird issues so immediately after launching the app the params weren't 'there', only after a small time period (had to move logic from created to computed). Dunno what could've caused this as in the past it worked fine |
We have encountered a problem that the deeplink is not surviving when going through the App Store.
When we set up a dynamic link which includes a deep link with specific path, users on iOS who downloaded the app do not get directed to the correct path defined on the deeplink.
The issue only occurs on iOS for the case that the user downloads the app.
How to reproduce:
deepLinkOpen
event is triggered but the deeplink url is missing.We suspect that the information about the deeplink is lost somewhere in the Apple App Store. For Android this works perfectly and has no issues.
Has anybody encountered similar issues? Anyone has any suggestions how to solve this?
Thanks!
The text was updated successfully, but these errors were encountered: