"Dynamic Link not found" is the error page Firebase Dynamic Links serves when a link's domain or path does not resolve, and since Google shut the service down on August 25, 2025, every Firebase Dynamic Link returns an HTTP 404, according to Firebase's Dynamic Links Deprecation FAQ read on 2026-11-22. The page tells the app's developer: "If you are the developer of this app, ensure that your Dynamic Links domain is correctly configured and that the path component of this URL is valid."
The error has a use on both sides of the link. It tells the developer which links to replace, and it tells the person who tapped it that the link is dead, not their phone. What a dynamic link not found page means depends on when the link last worked: before the shutdown it pointed to a setup mistake, and now it points to the shutdown itself. The firebase dynamic links shutdown stopped every link on page.link subdomains and on custom domains alike, so the fix is to move the links, not to repair them. Firebase dynamic links deprecated by Google still sit in emails, SMS, ads, QR codes and app code, and each one shows the error until it is replaced.
This page explains the error first, then what you can do as the person who tapped it, why the links stopped, which other links show the same page and what an app that still calls the SDK does. It then gives the developer fix, whether the old page.link domain can be kept, where to move the links and whether Firebase Authentication email links still work.
What does the "Dynamic Link not found" error mean?
The "Dynamic Link not found" error means the link was made with Firebase Dynamic Links, a service Google shut down on August 25, 2025, so the link no longer resolves to anything.
Before the shutdown, the same page had an older cause: a URL prefix or a path that was not set up in the Firebase console, the case asked about on Stack Overflow in September 2019 when a link failed with the app not installed. The date tells the two apart. A link that worked before late August 2025 and fails now is the shutdown; a link that never worked, on a project built before then, was a setup mistake.
What can you do when a link you tapped shows the error?
Nothing on your phone fixes a "Dynamic Link not found" error, because the link itself is dead. Three things get you to the content:
Ask for a new link: ask whoever sent the dead link for a new one to the same content.
Go direct: open the app or website yourself and search for the content the link pointed to.
Report it: tell the sender the link is broken if it came from a company, so the dead link gets replaced for everyone.
Why did Firebase Dynamic Links stop working?
Firebase Dynamic Links stopped working because Google shut the service down on August 25, 2025, for links on page.link subdomains and on custom domains alike. Google's Deprecation FAQ gives the reason: the native APIs the service was built on changed, which made its core feature, carrying a user into the app after install on any platform, hard to keep stable. The shutdown has three effects, per the FAQ:
Links fail: all Firebase Dynamic Links clicked return an HTTP 404 status.
APIs fail: the Short Links API and the Link Stats API return HTTP 400 or 403.
No new links: no new Firebase Dynamic Link can be created.
The FAQ says the error responses began gradually on August 25, 2025 and reach a 100% error rate after the sunset date, so a Firebase link that still redirects today is not a working link. Your own app's links are not the only ones affected.
Which links besides your own app's show the error?
Links made by other services on Firebase Dynamic Links show the same error: Google Calendar booking links in a May 2025 Reddit thread, and a forms.gle short link reported by cleanapp.io in October 2026. Google's goo.gl short links follow their own rule, set in Google's post "We're updating our plans for goo.gl links" of August 1, 2025: links that showed no activity in late 2024 stopped working after August 25, 2025, and "All other goo.gl links will be preserved and will continue to function as normal." The fix for these links sits with the service that made them, not with you.
What happens in an app that still calls the Dynamic Links SDK?
An app that still calls the Dynamic Links SDK does not crash, but every call fails or comes back empty. Google's Deprecation FAQ lists each call, Android first:
Use case | API call | Status code | What the app gets |
|---|---|---|---|
Android: create short link |
| 403 | An error with the failure reason |
Android: first open attribution |
| 400 | A success response with empty Dynamic Links data |
Android: reopen attribution |
| 400 | A success response with empty Dynamic Links data |
Android: accept invitation | AppInvite module in Google Play services | 400 | A spinner that disappears |
iOS: create short link |
| 403 | An error with the failure reason |
iOS: first open attribution | Called on | 400 | No error, but a Dynamic Links object with empty data |
iOS: reopen attribution |
| 400 | An error with the failure reason |
The user lands on the app's home screen instead of the shared content, and nothing in the crash reports shows it, which is why the fix starts with finding every link.
How do developers fix links that return Dynamic Link not found?
Developers fix links that return Dynamic Link not found by moving them to another service on a domain they control, since Firebase cannot serve them again. The firebase dynamic links migration runs in six steps:
Export your link metadata from Firebase, so you have every link and its destination.
Choose a service that covers the Firebase features your links used, such as deferred deep links or click analytics.
Recreate the links on a domain you control.
Swap the Dynamic Links SDK calls in the app for the new service's and ship a release.
Replace the old links in emails, SMS, ads, store listings and printed QR codes.
Delete the URL prefixes in the Firebase console.
The last step matters because, per Google's FAQ, deleting every URL prefix marks the Firebase project as having completed the migration and removes the console's reminder. The code for each step, with the API calls, is in the guide to migrate Firebase Dynamic Links to Smler.
Can you keep the old page.link domain?
No, you cannot keep the old page.link domain: Google's Deprecation FAQ says page.link domains are not available after the shutdown, cannot be kept or transferred, and recommends a new domain with another provider. Google marked the domain and link metadata for deletion on August 25, 2025, to be purged under its data retention policy.
Where do you move links that Firebase no longer serves?
You move links that Firebase no longer serves to another deep linking provider when they need full feature parity, or to Android App Links and iOS Universal Links when they only open an app that is already installed, as Google's Deprecation FAQ recommends. The FAQ names Adjust, Airbridge, AppsFlyer, Bitly, Branch, Kochava and Singular, providers "not vetted by Google". Smler is one more: its smart links route to the app, the store or the web, deferred deep linking is on the free plan with 25,000 attributed installs a month, and links never expire, according to Smler's comparison page read on 2026-11-22. The seven Firebase Dynamic Links alternatives are compared on deferred deep links, free limits and price, and the Smler Firebase Dynamic Links alternative page maps each Firebase feature to its equivalent.
Do Firebase Authentication email links break after the shutdown?
No, Firebase Authentication email links do not break after the shutdown: email link sign in, password reset and email verification keep working once the app runs the latest Firebase Authentication SDK, per Google's Deprecation FAQ. Android OAuth flows need at least Firebase Authentication Android SDK v20.0.0, and web apps are not affected, because the shutdown only changes how mobile devices handle incoming URLs.