Hi everyone,
We’re encountering an issue with a Custom Product Page (CPP) deep link configured in App Store Connect, and its execution seems inconsistent. Here are the scenarios we’ve observed:
1. If the app is already installed and I open it via the custom product page, the deep link executes as expected.
- ** If I install the app from the custom product page** and immediately open it, the deep link does not execute.
- If I install the app from the custom product page but wait 3+ seconds before tapping "Open," the deep link works as expected.
Additional context:
-
The deep link is processed in the SceneDelegate and points to an associated domain that redirects to a purchase funnel.
-
The behavior in (3) makes me suspect a timing issue.
The main challenge is debugging this, as testing the deep link’s execution requires installation from the App Store.
Does anyone have suggestions for improving the reliability of deep link execution in this scenario? Any insights into what might cause this timing-related behavior would also be greatly appreciated.
Thank you! Thomas
Thanks to the iOS Developer Support team, we were able to identify the root cause of the issue. They pointed us toward the Apple App Site Association (AASA) file, which is required for Universal Links to function. It appears that this file is downloaded asynchronously after app installation, leading to the observed delay in executing the deep link.
With this insight, we implemented a URL scheme deep link instead of relying on a Universal Link. Since URL schemes work immediately after installation, this resolved the problem entirely.
I would suggest adding a hint or recommendation in the Custom Product Pages deep link input field in App Store Connect to encourage the use of URL scheme links instead of Universal Links, particularly for scenarios where immediate link execution is critical.
