# page.link errors after the Firebase Dynamic Links shutdown, and how to fix each one

> Firebase Dynamic Links stopped on 25 August 2025, and it fails in different ways depending on where you look: a 404 page, 400 and 403 API errors, an empty getDynamicLink result, a spinner, broken email sign-in links. What each error means and how to fix it.

Source: https://straitlink.in/blog/page-link-errors-firebase-dynamic-links-fixes/

Firebase Dynamic Links (FDL) did not fail in one tidy way when Google shut it down on **25 August 2025**. People who tap an old link see one thing, your backend logs show another, and your app shows a third: often nothing at all, because the SDK hands back an empty result instead of an error. Google's [Dynamic Links deprecation FAQ](https://firebase.google.com/support/dynamic-links-faq) has a table of exactly what each call now returns. This post walks through that table, one error at a time, with what it means and what to do about it.

If you want the cleanup plan (finding every old link, importing them, swapping the SDK), read our [page.link migration checklist](https://straitlink.in/blog/page-link-links-404-migration-checklist/) first. This post is the reference for when something is already failing and you need to know why. For a dated overview of what still works after the shutdown, see [Firebase Dynamic Links shutdown: what still works](https://straitlink.in/blog/firebase-dynamic-links-shutdown-what-still-works/).

## Quick reference

| Where you see it | What you see | What it means |
|---|---|---|
| A person taps a short page.link URL | Either HTTP 404 ("Dynamic Link Not Found") or a plain redirect to the old fallback | Gone from Google's side, or a plain redirect; an app build that keeps the page.link domain can still open it |
| A person taps a long page.link URL (`?link=…`) | HTTP 400, "Invalid Dynamic Link - Blocked" | The link no longer resolves |
| Your server calls the Short Links API | HTTP 400 or 403 | Link creation is switched off |
| Your server calls the Link Stats API | HTTP 400 or 403 | Analytics are switched off |
| App code calls `buildShortDynamicLink` or `shorten` | A 403 error with a failure reason | In-app link creation fails |
| Android `getDynamicLink(intent)` | A successful task with **empty** data | The app opens, but on the wrong screen |
| iOS first-open attribution | An FDL object with **empty** data, no error | Deferred links never arrive |
| iOS `handleUniversalLink` | An error (400 behind it) | Opens from a link lose their destination |
| An Android tap handed to Google Play services | A spinner that disappears | The old invite flow has nothing to show |
| Firebase Auth email links | Sign-in, reset or verify links misbehave | The Auth SDK still points at FDL |

The rest of this post takes each row in turn.

## "Dynamic Link Not Found" (HTTP 404), and links that still redirect

This is what your users see. Google's FAQ says that after the shutdown "all links clicked will return a HTTP 404 status response to end users", on page.link subdomains and on custom domains that FDL served. Real links are less uniform. When we requested page.link URLs from several apps on 5 October 2026, some short links returned `404` with a page titled "Dynamic Link Not Found", others still answered with a plain `302` to their web or Play Store fallback, and a long `?link=…&apn=…` link returned `400`. A short link that still redirects no longer opens the app or carries the deep link through an install, and Google could stop that redirect at any time.

```bash
curl -s -o /dev/null -w '%{http_code} %{redirect_url}\n' https://yourapp.page.link/abc
# 404, or 302 to the old fallback URL
```

**The fix depends on the domain.**

- **On a page.link subdomain**, nothing can bring the deep link back. The FAQ says page.link domains "will no longer be available", and they can't be kept or transferred. What you can do is replace the URL wherever you still control the text: app share code, email and push templates, SMS templates, your website, store listings and social bios. Printed QR codes need a reprint.
- **On a custom domain you own**, you can point the domain at a new provider and recreate the same paths, so old links start working again. The FAQ has one extra note here: if FDL used Firebase Hosting on that domain, the `firebase.json` rewrite rules may still send those paths to Dynamic Links, so update the rewrites and redeploy Hosting before you expect the new provider to answer.

To sort a long list of old links quickly, paste them into the free [page.link checker](https://straitlink.in/tools/page-link-checker/). It runs in your browser, marks which links were Firebase links, pulls the destination out of every long link's `link=` parameter, and flags the short links whose destination only Firebase knew. Those need your own records.

## Short Links API: 400 or 403

If your server created links on the fly (invites, referral links, order links) it called `https://firebasedynamiclinks.googleapis.com/v1/shortLinks`. The FAQ says every request there now returns **400 or 403**. Google also says these errors started gradually on 25 August 2025 and rose until every request failed, so if a dashboard showed "some invites fail" in late August, that was the cause.

**Fix:** find every caller (search server code and environment files for `firebasedynamiclinks.googleapis.com`), replace it with your new provider's API, and decide what the code should do when link creation fails. A 403 that bubbles up as a crash in a checkout or invite screen is worse than a plain web URL. On Strait the replacement is `POST /v1/links` with a secret key, from your server only. The request and response are in the [API reference](https://straitlink.in/docs/api/).

## Link Stats API: 400 or 403

The same applies to `…/v1/SHORT_DYNAMIC_LINK/linkStats`. Scheduled jobs that pulled link statistics into a warehouse now fail every night.

**Fix:** switch the job off. Google said your link metadata would be "marked for deletion" on the shutdown date and purged under its data retention policy, so there is nothing left to pull. New numbers come from the new provider. On Strait, taps, installs and app opens are in [Analytics](https://straitlink.in/docs/analytics/), and the full history can be exported.

## In-app link creation: a 403 error

On iOS, `shorten`, `shortenUrl` and `shortenWithCompletion` now emit an error with a failure reason, backed by a 403. On Android, `buildShortDynamicLink` does the same. This usually shows up as a share button that stops doing anything.

**Fix:** remove the call and create links another way. The safe pattern is to have your server create the link (keep secret keys off the phone), or to share a plain web URL on your verified domain. On Strait, the app SDKs use a publishable key that can't create or change links. That's intentional, so a key pulled out of your app can't be used to make links on your domain.

## Android: getDynamicLink succeeds, but the data is empty

This is the error people miss, because it isn't one. Google's table says `getDynamicLink(getIntent())` returns "a success response, but FDL data will be empty", for both first-open and reopen cases. The app launches, your listener runs, the link is `null`, and the user lands on the home screen. Nothing is logged as a failure.

**Fix:** stop relying on FDL to deliver the link and remove the SDK (`com.google.firebase:firebase-dynamic-links` on Android, `firebase_dynamic_links` in Flutter, `@react-native-firebase/dynamic-links` in React Native). Then route on your new provider's callback. With Strait that's one `onLink` callback for both cases: a tap that opens the installed app, and the first open after an install. On Android the link travels through the install inside Google Play's install referrer, so the first open gets the exact link rather than a guess. The [deferred deep linking docs](https://straitlink.in/docs/deferred-deep-linking/) show what your app receives.

Until the new release reaches everyone, treat an empty link as normal: open a sensible screen and don't show an error.

## iOS: first open returns nothing, handleUniversalLink errors

On iOS the FDL SDK used to check for a deferred link automatically when `FirebaseApp.configure()` ran. Google's table says that check now gets a 400 and "no errors are emitted, but an FDL object is sent back with empty data". So new installs never get their link, silently. `handleUniversalLink`, used when an installed app is opened from a link, now emits an error.

**Fix:** remove the `FirebaseDynamicLinks` pod or Swift package product, and change Associated Domains from `applinks:yourapp.page.link` to your new link host. Then check the `apple-app-site-association` file with the free [AASA validator](https://straitlink.in/tools/aasa-validator/). On Strait, iPhone links were tested on a real iPhone in October 2026. Deferred matching is opt-in: proven on iPhone simulators, with the real-iPhone run waiting on our App Store listing, and we label it that way.

## A spinner that appears and disappears (Android)

Google lists one more Android case: when the old AppInvite module in Google Play services handles a tap on a page.link or custom FDL domain, it "shows a spinner when Google Play Services is invoked and disappears when a 400 response is returned". Users read this as "the app is broken".

**Fix:** remove the intent filter that sends your page.link host into the app, and ship links on a new verified host. Old app versions keep the old filter until people update, which is one more reason to ship the new release before you swap links in templates.

## Firebase Auth email links

If you use email link sign-in, password reset or email verification, FDL was part of those links. Google's FAQ says these actions "will continue to work", but you need to upgrade to the latest Firebase Authentication SDKs and migrate to the new setup. It links separate [Android](https://firebase.google.com/docs/auth/android/email-link-migration) and [iOS](https://firebase.google.com/docs/auth/ios/email-link-migration) guides. It also says onboarding to Dynamic Links for email link sign-in is no longer possible.

**Fix:** follow those guides. This isn't a deep-linking provider problem, and swapping providers won't fix it.

## "Will my app crash?"

Google's answer is no: "The SDKs themselves will not cause your app to crash. Your application code must handle the changed API responses." In practice a crash comes from your code assuming a link is present, for example force-unwrapping a `nil` URL in Swift or calling a method on a `null` link in Kotlin. Search for every place that reads the dynamic link and make the empty case safe before you do anything else. It costs little and should come first.

## After the fixes: check on a phone

Once the new SDK and domain are in, test from a chat or email app, not by pasting into an address bar:

- App installed: the link opens the right screen.
- App not installed: the store, then the right screen on first open.
- Opened inside Instagram or WhatsApp: see [why in-app browsers break deep links](https://straitlink.in/blog/instagram-whatsapp-links-open-browser-not-app/).

If a link opens the browser instead of the app on Android, verification failed. The [App Links checker](https://straitlink.in/tools/app-links-checker/) fetches your `assetlinks.json` and `apple-app-site-association` and explains what's wrong. For the full move, code for every platform is in [Migrate from Firebase Dynamic Links](https://straitlink.in/docs/migrate-from-firebase/).

## Sources and how we checked

- Google, [Firebase Dynamic Links deprecation FAQ](https://firebase.google.com/support/dynamic-links-faq): the shutdown date, the stated 404 response, the 400/403 API responses and their gradual start, the per-SDK table (status codes, empty data, the spinner, the no-crash note), page.link domains, the `firebase.json` rewrite note, metadata deletion, and the Firebase Auth section. Read on 5 October 2026.
- Google, Firebase Auth email link migration guides for [Android](https://firebase.google.com/docs/auth/android/email-link-migration) and [iOS](https://firebase.google.com/docs/auth/ios/email-link-migration), linked from the FAQ.
- Our own requests to real page.link URLs on 5 October 2026 with `curl`: some short links returned HTTP 404 ("Dynamic Link Not Found"), others a plain `302` to their web or Play Store fallback; a long `?link=…&apn=…` link returned `400`.
- Strait behaviour (publishable and secret keys, `onLink`, the Play install referrer, iPhone install matching) as documented in our [keys](https://straitlink.in/docs/keys/), [deferred deep linking](https://straitlink.in/docs/deferred-deep-linking/) and [migration](https://straitlink.in/docs/migrate-from-firebase/) docs.
