11

I have been reading around and found a couple of existing answers about apple-app-site-association caching:

These answers all indicate that the association file is fetched from the web on install/update only.

This is worrisome to me because it means that I need to sync updates to the file with releases of my app.

It also means that if some URLs that I do not want universally linked (e.g. my contact page's, /contact) were not initially blacklisted from my association file, users that do not update my app will have a broken experience forever when trying to access that page.

My question is: does anyone here know of a way to force my app to update its association file without needing to release a new version and wait for all my users to update?

Edit and also, why?

Sir Celsius
  • 822
  • 8
  • 22
  • Does this answer your question? [Does the apple-app-site-association json file ever get updated in app?](https://stackoverflow.com/questions/35187576/does-the-apple-app-site-association-json-file-ever-get-updated-in-app) – Trevor Dixon Feb 14 '23 at 18:00

1 Answers1

6

It is not possible to force this. Apple does not disclose the update criteria, but working with this all day, I can assure you that install/update are the only times I've ever seen this file scraped.

A better alternative is to use a hosted deep link platform like Branch.io (full disclosure: I'm on the Branch team), because then you don't need to worry about updating the apple-app-store-association config after it's set the first time.

Alex Bauer
  • 13,147
  • 1
  • 27
  • 44
  • Hey Alex, thanks for the info. We already use Branch, but in this case, the damage is done for all users that got the broken association file on their first install. I'll accept your answer for now and wait until a majority of my users have updated their apps I guess :( – Sir Celsius Jul 31 '17 at 08:32
  • Ugh yes that's frustrating. Hopefully with auto updates, it won't take too long. – Alex Bauer Jul 31 '17 at 12:02