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
We share that link with to test the deep linking feature of OneLink.
What did you expect to happen?
When the app is already installed, we expect the app to be automatically opened, the deep link to be resolved, and then our custom logic is executed based on the data retrieved from the query params.
What happened instead?
On Android devices this works exactly as expected, the app initially opens to the home screen, the deep link is resolved along with the query param data, and we navigate the user to the expected location based on the data.
On iOS, when the app is launched from the link, it tried to open to a page that matches the URI in the OneLink URL, for example /WGMu/j8ekkwge
Please provide any other relevant information.
When reviewing the logs of the device, we can see the data from the params in the link is available, but because the app is initially opened to this non-existing page, our code is not executed, and we cannot navigate the user to correct location.
We noticed that the data from the OneLink link is resolved differently when comparing the logs of a Android device and iOS device
iOS logs:
Android Logs:
The main difference (I think) is that the "link" value in android is pickem:// which results in the app opening to the home page initially, but on iOS the "link" value is the full https:// url which results in the app opening to the path in the URI .
The text was updated successfully, but these errors were encountered:
👋 Hi @BennyG93 and Thank you for reaching out to us.
In order for us to provide optimal support, please submit a ticket to our support team at [email protected].
When submitting the ticket, please specify:
Report
Plugin Version
"expo": "~50.0.17",
"react": "18.2.0",
"react-native": "0.73.4",
"react-native-appsflyer": "^6.14.3",
On what Platform are you having the issue?
iOS
What did you do?
We generate a branded OneLink link either manually in the AppsFlyer dashboard or programatically using
generateInviteLink()
.It will look something like: https://invite.pickem.social/WGMu/j8ekkwge
We share that link with to test the deep linking feature of OneLink.
What did you expect to happen?
When the app is already installed, we expect the app to be automatically opened, the deep link to be resolved, and then our custom logic is executed based on the data retrieved from the query params.
What happened instead?
On Android devices this works exactly as expected, the app initially opens to the home screen, the deep link is resolved along with the query param data, and we navigate the user to the expected location based on the data.
On iOS, when the app is launched from the link, it tried to open to a page that matches the URI in the OneLink URL, for example
/WGMu/j8ekkwge
Please provide any other relevant information.
When reviewing the logs of the device, we can see the data from the params in the link is available, but because the app is initially opened to this non-existing page, our code is not executed, and we cannot navigate the user to correct location.
We noticed that the data from the OneLink link is resolved differently when comparing the logs of a Android device and iOS device
iOS logs:
Android Logs:
The main difference (I think) is that the
"link"
value in android ispickem://
which results in the app opening to the home page initially, but on iOS the"link"
value is the fullhttps://
url which results in the app opening to the path in the URI .The text was updated successfully, but these errors were encountered: