Posts

Post not yet marked as solved
50 Replies
Would you mind posting your AASA file URL? I am also investigating this issue for my apps. One thing I notice the difference is the hosts accepting http/1.1 working fine ("ALPN, server accepted to use http/1.1") with compare to the ("ALPN, server accepted to use h2").In my device, lot of domains are failing to load the AASA files and randomly checking on the patterns using curl command, I find the same difference. May be some hint for all of you who are investigating this issue. In case you find any solution please do reply here.
Post not yet marked as solved
50 Replies
Assuming you are supporting all paths in your domain, try setting path in AASA as -"paths": ["NOT /e/*", "*","/"]Hope this helps
Post not yet marked as solved
5 Replies
I was facing the same issue. However, when I noticed the AASA file, then my app identifier was different than expected. So make sure you don't have explicit app identifier for your app in enterprise portal. Best way to verify is to have the same app id in Provision Profile and AASA file.This solved my problem and links are working great.