I've been working trying to get Universal Links working for the past few days and it has been an adventure. Using the App Search API Validation Tool has been challenging. I've seen many posts from others looking for "why" their AASA file has been rejected. When I compare AASA files (I've only been able to find 1 so far that passes and that is Twitter. What would really help (in my opinion) would be to give more information regarding what this tool does and what are the factors are. I find the error messaging very opaque. Answers to Error cannot parse app site association well if it's valid JSON, why can't the service say what it doesn't like? What does it mean that no apps associated with url, does it mean that no apple bundle can be found on the app store? Does it mean Universal links will not work, period? I get a sense that there is a lot going on under the hood that is just not described. If that could be exposed that would really be helpful. Giving devs an idea of how frequently they can do the validation check would be nice. What is the relationship between the deployed bundle and validation. When I test my AASA file, is it testing what's on the website or is going to the CDN? Maybe give output describing which schema versions and therefore which IOS versions are supported would be great. I don't want to sound critical, but I was able to get the android version working with hardly any external blogs. I'm currently at this point right now... Error no apps with domain entitlements The entitlement data used to verify deep link dual authentication is from the current released version of your app. This data may take 48 hours to update. I guess I'll come back in a few days to retry. Anyway, don't want to sound like I'm venting. I think some rough edges could be smoothed over with just a few paragraphs of documentation. Thanks