Your deep links are opening Safari. No crash, no log, no alert. Check any domain, free.
Apple’s CDN caches its own copy and serves it to every iPhone. A blocked bot, a stray redirect, a stale cache — Apple sees something your browser never will.
Browser says yes. Phone says no. Only one ships your revenue.
/.well-known/ and the legacy root — whichever Apple used.
The file every device reads, plus Apple’s failure headers, verbatim.
We fetch as Apple, as a device, as a browser — and compare.
TeamID.bundleID in Apple’s copy, not the one on disk.
Each link through Apple’s matcher. App, excluded, or Safari.
Deployed a fix? See if it’s actually live on devices.
Validators check your origin once. We check the copy Apple's CDN actually serves devices, fetch as Apple's own client to catch bot-blocking, and re-check on a schedule — then alert.
No. Read-only GET of a file you published for Apple to fetch. Same thing an iPhone does.
Because Apple's enforced behaviour ≠ its docs. octet-stream and https→https redirects work fine; we WARN where others hard-fail, and say why.
Origin → Apple's CDN: up to 24h. CDN → device: ~weekly. No way to force it. We turn that opaque wait into a countdown.