We are testing Apple Universal Links for ios.aierchina.com. The domain is ICP-registered and hosted in mainland China. The problem: Apple's CDN always returns “not found” for our AASA file: https://app-site-association.cdn-apple.com/a/v1/ios.aierchina.com What we have verified: The AASA file is correctly served at both /.well-known/apple-app-site-association and /apple-app-site-association Returns HTTP 200, valid JSON, correct Content-Type, no redirects, valid SSL Server response time is under 500ms What works: Adding ?mode=developer to the applinks entry works perfectly Universal Link Diagnostics on device (ios.aierchina.com/uat) correctly resolves to our app bundle What does not work: Production mode fails because the Apple CDN never caches our AASA file Reinstalling the app does not help Server logs show occasional requests from com.apple.swcd, but CDN still returns 404 Questions: Are there known issues with Apple CDN caching AASA files for China-hosted domains? Is there any way to force Apple's CDN to re-crawl our domain? Could the GFW or regional network policies be interfering? What was the fix?
Apple's CDN always returns “not found”
Thank you for your post.
When I make a request to your server to download the AASA file I do not get an answer:
curl -v https://ios.aierchina.com/.well-known/apple-app-site-association
* Host ios.aierchina.com:443 was resolved.
* IPv6: (none)
* IPv4: 58.20.15.12
* Trying 58.20.15.12:443...
* connect to 58.20.15.12 port 443 from 17.193.106.152 port 64699 failed: Operation timed out
* Failed to connect to ios.aierchina.com port 443 after 75012 ms: Couldn't connect to server
* Closing connection
curl: (28) Failed to connect to ios.aierchina.com port 443 after 75012 ms: Couldn't connect to server
If the server can't be requested from any IP or user-agent, the CDN servers won't be able to download the AASA file.
Please take a look at the Tech Note for Universal Links.
TN3155: Debugging universal links | Apple Developer Documentation
Hope this helps
Albert WWDR
Thank you for your help. We identified the issue: our server may be restricting overseas access.