Lately few user devices started to fail opening universal links after a fresh app install.
After checking, I noticed that aasa format has been updated. so i added the new appIDs and components arrays but then apple api validator started to fail and started to say cannot parse aasa.
Also got a clue after checking server logs, that users fetching aasa from our servers manage to open links. However for those who fail to open the links there is no aasa request to our server so i assume that they are getting from apple aasa cdn.
I have absolutely no clue on what to do because this aasa validation and apple cdn is a black box with no information to help in debugging.
Here is my failing aasa:
"applinks": {
"apps": [],
"details": [
{
"appIDs": [ "D5LU2VMPV6.com.popperpay.popperios.demo"],
"appID": "D5LU2VMPV6.com.popperpay.popperios.demo",
"components": [{"/": "/*"}],
"paths": [ "*", "/" ]
}
]
}
However this one is parsed:
"applinks": {
"apps": [],
"details": [
{
"appID": "D5LU2VMPV6.com.popperpay.popperios.demo",
"paths": [ "*", "/" ]
}
]
}
Selecting any option will automatically load the page