Root files (.well-known) served via cdn.bubble.io URLs, breaking Universal Links & App Links

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:

  1. Upload .well-known/apple-app-site-association.json or .well-known/assetlinks.json under Settings > SEO / metatags > Hosting files in the root directory.

  2. 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.

  3. 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.

In the past, both links was working. Send a support ticket

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

Have you submitted a bug report? Contact | Bubble is the best place and will ensure they can fix the bug!

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.

Support (Louis) confirmed the bug with paths containing “.” and escalated it to engineering with high urgency. I’ll keep this thread updated!

Im having the same issue over here. Bubble please solve this as soon as possible.. All deeplinks features are disabled now

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.

Bubble whats going on guys? this is a MAJOR issue! please give us an update on this fix

Good morning everyone, I’ll be taking a look and hopefully find some updates to share

okay update for everyone following this thread:

  • Fix is ready to deploy
  • Deploy is blocked by important platform upgrades
  • Those upgrades are critical work related to the outages we had weeks prior, so they take priority
  • I will have another update later today

Later today update:
Fix was deployed!

I can confirm that it’s working properly now! Thank you for the fix!