I have a domain name hosted by BASE 44 for the app; this is needed for Google Play Store deep link verification. When fixing a deep link verification, the roadblock was
the .well-known/assetlinks.json. The in-app AI suggested contacting support, which I did, and it came back with this: see below. There are workarounds; it would help many builders to have this integrated already.
Thanks for reaching out. I completely understand what you're trying to accomplish — the
.well-known/assetlinks.json
path is required for Android App Links (Digital Asset Links) verification with Google Play.
Unfortunately, I'm not able to configure custom URL rewrites or routing rules on your behalf — this isn't something support agents can do directly on the platform side.
That said, here's a workaround that should achieve the same result without needing a URL rewrite:
The approach: Instead of a rewrite, you can make your
assetlinks
backend function responds directly to the correct path by serving the JSON content in a way Google Play can verify. However, since Base44 functions are served under
/functions/
, the path won't match
.well-known/assetlinks.json
directly.
The most reliable workaround is to host the
assetlinks.json
file externally and point to it. Here are your options:
Host on GitHub Pages or similar — Upload your assetlinks.json
to a static host and serve it at the exact .well-known/assetlinks.json
path, then use a redirect from your Base44 app if possible.
Try asking the AI chat with a more specific prompt — Sometimes framing the request differently helps:
Create a backend function that serves the assetlinks.json content needed for Google Play Store deep link verification. The function should return the correct JSON with Content-Type: application/json headers.
Then in Google Play Console, you can sometimes specify a custom assetlinks URL path.
Use a Cloudflare Worker or similar proxy — If your domain DNS goes through Cloudflare, you can add a Worker or Page Rule that intercepts /.well-known/assetlinks.json
and proxies it to your Base44 function.
I'd also suggest submitting this as a feature request on the Base44 Feedback board — custom path routing / URL rewrites for well-known paths is a legitimate need for app store integrations and would benefit many builders.
Please authenticate to join the conversation.
In Review
Feature Request
5 days ago

Zana Grant
Get notified by email when there are changes.
In Review
Feature Request
5 days ago

Zana Grant
Get notified by email when there are changes.