One file for each domain, both www.example.com and example.com need separate files:
{
"applinks": {
"apps": [],
"details": {
"9JA89QQLNQ.com.apple.wwdc": {
"paths": [
"/wwdc/news/",
"/videos/wwdc/2015/*"
]
}
}
}
}
- Fall back gracefully
- If cannot handle, open Safari
UIApplication.sharedApplication().openURL(webURL)
There is no guarantee that the user experience with custom URL schemes will remain the same in the future. Smart App Banners afford the preferred experience.
https://developer.apple.com/videos/wwdc/2015/?id=509
<head>
<meta name="apple-itunes-app" content="app-id=640199958, app-argument=https://developer.apple.com/wwdc/schedule, affiliate- data=optionalAffiliateData">
</head>
I've found that the apple-app-site-association file is fetched when the app is installed on the device. So essentially, every install/update will trigger a download of the file. You can simulate this by deleting the app from your device and reinstalling it.
do you know if there is any actual reference documentation somewhere? Even latest is using components key now https://developer.apple.com/documentation/bundleresources/applinks
is
*
the only matching operator? Does order matter? Will an exclude stop evaluation on remaining paths?