Summary: Recently, files hosted under “Hosting files in the root directory” (such as .well-known/apple-app-site-association.json and .well-known/assetlinks.json) are being converted or redirected to cdn.bubble.io URLs instead of being served directly from the main domain origin. Because iOS Universal Links and Android App Links strictly require these validation files to be served directly from the domain root without cross-origin redirects/CDN host swaps, deep linking integration has broken.
Steps to Reproduce:
Upload .well-known/apple-app-site-association.json or .well-known/assetlinks.json under Settings > SEO / metatags > Hosting files in the root directory.
Access [https://yourdomain.com/.well-known/apple-app-site-association.json](https://yourdomain.com/.well-known/apple-app-site-association.json) or check the rendered URL.
Observe that the file URL is converted/redirected to https://<hash>.cdn.bubble.io/.../apple-app-site-association.json?....
Expected Behavior: The file content should be served directly from [https://yourdomain.com/.well-known/](https://yourdomain.com/.well-known/)... under the custom domain origin with an HTTP 200 response.
Actual Behavior: The file URL points to an external cdn.bubble.io host, which causes Apple and Google verification servers to reject the file.
Impact:
iOS Universal Links and Android App Links fail domain verification.
Native app deep-linking features stop functioning completely.
I have the same issue. We can’t make universal links work for a Natively wrapped app which is frustrating and embarrassing at the same time. We need a fix ASAP
I’m having the same issue. My TWA app on Google Play
stopped hiding the URL bar because
/.well-known/assetlinks.json returns 404 on my custom
domain (app.foodpage.com.br), even though the file is
correctly uploaded in Settings → SEO/metatags → Hosting
files in the root directory and deployed to live.
The manifest.json in the root works fine — only the
.well-known path is broken.
This was working before. Please fix this urgently as it
breaks Android App Links verification.
It has been 5 days since the bug was confirmed, yet there is still no update or fix. Progress feels far too slow for an issue that breaks core functionality for so many users.