My app has three separate environments named
- int
- sbx
- prod
Here are my three AASA files on my webservers.
Here are the same three AASA files on Apple's CDN
I have two questions.
- How can I invalidate the Apple CDN so that my new AASA files are pulled in?
- Do my new AASA files look like they will support all possible paths? Does * capture any path e.g., /collection/123, /wallet/oauth?code=123, /sign-in
I've done the generic Googling and docs reading around this. I can't seem to find anything specifically related to Apple's CDN.
61 Answer
Updating my AASA file's Cache-Control header to no-cache fixed this for me.
I use Next.js, so here is my next.config.js that fixed this for me.
{ source: "/.well-known/apple-app-site-association", headers: [ { key: "Content-Type", value: "application/json" }, { key: "Cache-Control", value: "no-cache" }, ], },