Invalid Dynamic Link: What It Means and How to Fix It
Password reset and verification links on page.link hosts are dead. The SDK, domain and fingerprints that must agree before the link reaches your app.
Invalid Dynamic Link appears when a link issued by Firebase Dynamic Links stops resolving. Google shut the service down on August 25, 2025, and its deprecation FAQ says clicked links "will return a HTTP 404 status response to end users." Anything generated on a *.page.link host went with it, and no console setting brings those URLs back.
We have not traced which screen prints that exact wording, because Google documents the outcome as a 404 rather than a named error page. The fixes below follow the shutdown behavior Google describes, and the first section works out which case you are in.
Which problem is throwing the error
| What the user sees | Cause | Go to |
|---|---|---|
| A reset, verification or sign-in email link fails on a phone | Firebase Authentication still generating links on a dead page.link host | The email link case |
A shared short link or long ?link= URL shows a 404 |
Firebase Dynamic Links no longer exists | What to do first |
| The app opens but link data is empty | a dead link returning an empty result | The failure that shows no error |
| "Invalid dynamic link blocked" after tapping a Maps link | reported on a Maps help thread; no cause documented there | Maps support |
| Adobe "Dynamic Link Server" or a DLL message | Adobe software or Windows | not covered here |
Searches for this failure also arrive as "dynamic link not found", which is the 404 people land on.
If your error mentions Adobe, Premiere, After Effects or a missing DLL, this page will not help. Those are unrelated products and errors.
What the shutdown changed
If the term is new to you, what a dynamic link is covers the basics. What changed is that the link management APIs went with the service: the Short Links and Link Stats APIs return 400 or 403 after the shutdown, so scripts that create links fail too.
You cannot keep or transfer a page.link domain, and there is no forwarder to configure. Every copy of those URLs, in email templates, SMS campaigns and store listings, points at the same dead host.
A domain you own is different, because you keep it. Google's advice is to export your link metadata and recreate the links on a new domain. If you reuse that domain with a new provider, the FAQ notes you may need to update your firebase.json rewrite rules and redeploy before the new paths answer.
The email link case
This is the case that breaks a user-facing flow. Firebase Authentication used Dynamic Links to serve password resets, email verification and email-link sign-in on mobile. Google moved that to the project's Firebase Hosting default domain, in Authentication Android SDK 23.2.0+ and BoM 33.9.0+ and the iOS SDK 11.8.0+.
Two things have to change: the SDK version, and the domain the project generates links on.
That domain is project configuration, and you change it once with Admin SDK credentials:
import { getAuth } from 'firebase-admin/auth';
await getAuth()
.projectConfigManager()
.updateProjectConfig({ mobileLinksConfig: { domain: 'HOSTING_DOMAIN' } });
domain is an enum with two values, HOSTING_DOMAIN and FIREBASE_DYNAMIC_LINK_DOMAIN, so you pass the literal rather than a hostname. Google's migration page describes this call as how you tell the backend to generate links on the Hosting domain. It documents no console setting for it.
While you are in the code, remove dynamicLinkDomain from ActionCodeSettings. Google documents that field as "Deprecated. Don't specify this parameter." Its replacement is linkDomain, which you specify to select a custom Hosting domain and which otherwise falls back to the default, PROJECT_ID.firebaseapp.com.
Three things then have to agree before a reset link reaches the app:
- The link is generated on the Hosting domain, which the Admin SDK call above sets.
- The domain in your
urlvalue, the continue URL, is listed under Authentication, then Settings, then Authorized domains. Auth uses that list to validate where the action link sends people. - Your app claims the Hosting domain in Associated Domains on iOS or in the intent filter on Android, and the Android package name plus its SHA-1 and SHA-256 certificate fingerprints are registered in the Firebase console. Without this step the link opens a browser instead of the app.
Web email actions are not part of this. Google's FAQ answers "Are Firebase Authentication email actions on web apps impacted?" with "No," because the change only affects handling incoming URLs on mobile devices. If a browser-based reset works and the app one does not, the fault is in the three steps above.
The failure that shows no error
Not every dead link announces itself. The FAQ's table says Android's getDynamicLink(getIntent()) returns a success response with FDL data empty, and iOS first-open attribution returns an FDL object with empty data. iOS reopen attribution behaves differently and emits an error.
So the shape of the bug depends on the platform and the entry point. The listener fires with an empty link, and the user lands on the home screen. Google's table lists no crash for any of these calls, so the failure shows up in your own handling and never in crash reports.
If link volume reads zero while installs look normal, check whether you are reading an empty result as success. Treat a null or empty payload as a failed resolution, log it, and route the user to a default screen.
If the host is not page.link
- If the host is your own domain, check whether your new provider serves those paths and whether
firebase.jsonstill routes them to Dynamic Links. - If the host is a Hosting domain and the link opens a browser, compare that domain against Authorized domains and against your association file.
Google's debugging page documents an iOS self-diagnostic call and a ?d=1 preview parameter. Neither works on a link the backend no longer serves.
What to do first
- Grep your app and templates for
page.link. Every URL you find is dead and needs reissuing. - Upgrade the Authentication SDK on both platforms, then switch the link domain with the Admin SDK call above.
- Remove
dynamicLinkDomainfrom yourActionCodeSettingsand setlinkDomaininstead. - Add the continue URL domain to Authorized domains, register the Android package name and certificate fingerprints, and ship the matching Associated Domains or intent filter change.
- Reissue what you cannot edit, including QR codes that point at page.link, which have to be reprinted on a domain you control.
If you are rebuilding on your own domain and want click and install data under the link, we built ChottuLink for that, and our migration guide walks through the move. We are independent of Google and Firebase.