動態鏈接棄用常見問題解答

我們在 7 年前推出了 Firebase 動態鏈接,以使 URL 更加強大 - 例如,根據運行時條件動態更改鏈接的目標。

多年來,網路和行動生態系統隨著App LinksGoogle Play InstantUniversal LinksApp Clips等技術的發展而不斷發展,並使應用程式使用者在應用程式和網路上的用戶旅程變得更加無縫和可預測。我們相信,您和您的用戶將透過直接採​​用這些技術並繼續推動生態系統向前發展而受益更多。然而,除了這些新變化之外,Firebase 動態連結所基於的原始本機 API 也在不斷發展並帶來了新的挑戰。

例如,生態系統的變化影響了我們為 Firebase Dynamic Links 的核心功能之一提供一致穩定的體驗的能力 - 讓應用程式使用者在安裝後順利過渡到應用程序,無論平台如何。

我們不再繼續支援不太理想的體驗,而是決定取消 Firebase 動態鏈接,並將我們的資源重新集中在解決其他開發人員痛點上。

我們了解,這項變更將需要您花時間評估和採用市場上的替代解決方案或平台提供者。

隨著生態系統的不斷發展和變化,我們將繼續發展 Firebase 以滿足您的需求。我們將繼續在 Firebase 產品中推出新功能和更新,並致力於協助您在應用程式開發之旅中脫穎而出。

我需要知道什麼?

2025 年 8 月 25 日,Firebase 動態連結將關閉。 Firebase 動態連結(託管在自訂網域和 page.link 子網域上)提供的所有連結都將停止運作,您將無法再建立新連結。

為了幫助您決定如何從Firebase 動態連結進行遷移,我們將繼續更新此常見問題解答文檔,提供供您考慮的其他信息,並提供可能與您當前使用Firebase 動態連結的方式相匹配的不同遷移場景的遷移指南。

隨著棄用日期接近 2025 年 8 月 25 日日落日期,我們還將繼續更新本指南,提供更多常見問題解答,並在幫助支援您的遷移工作時發現任何其他問題。

請參閱下面的常見問題解答,以幫助回答您的一些最重要的問題。

要開始遷移,請查看下面的「我應該如何從服務遷移」常見問題

2025 年 8 月 25 日,Firebase 動態連結將關閉。 Firebase 動態連結提供的所有連結(託管在自訂網域和 page.link 子網域上的連結)都將停止運作。

我需要多長時間進行遷移?

您必須在 2025 年 8 月 25 日之前完成遷移。

是的,您的新連結和現有連結將繼續有效,直到動態連結服務於 2025 年 8 月 25 日關閉為止。

當 Firebase 動態連結停用後,您可以預期:

  • 點選的所有連結都會向最終使用者傳回 HTTP 404 狀態回應。
  • 所有 HTTP 請求:

    • https://firebasedynamiclinks.googleapis.com/v1/shortLinks(短連結 API)
    • https://firebasedynamiclinks.googleapis.com/v1/SHORT_DYNAMIC_LINK/linkStats(連結統計 API)

    將傳回 400/403 HTTP 狀態回應。

  • 以下行為是基於您的應用程式中進行的 SDK 平台版本和 API 呼叫:

    iOS系統

    使用案例API呼叫狀態碼行為您的應用程式會崩潰嗎?
    建立短連結

    縮短(斯威夫特)

    縮短網址(Swift)

    縮短完成(Objective-C)

    400發出錯誤並說明失敗原因不*
    首次開放歸因

    FirebaseApp.configure (Swift) / FIRApp.configure (Objective-C) 上自動調用

    400不會發出錯誤,但會傳送回帶有空資料的 FDL 對象不*
    重新開啟歸因

    處理通用連結(Swift)

    處理UniversalLink (Objective-C)

    400發出錯誤並說明失敗原因不*

    安卓

    使用案例API呼叫狀態碼行為您的應用程式會崩潰嗎?
    Create Short Link

    buildShortDynamicLink (Kotlin)

    buildShortDynamicLink (Java)

    400 Error is emitted with failure reason不*
    First Open Attribution

    getDynamicLink(getIntent()) (Kotlin)

    getDynamicLink(getIntent()) (Java)

    400 Task returns a success response, but FDL data will be empty不*
    Reopen Attribution

    getDynamicLink(getIntent()) (Kotlin)

    getDynamicLink(getIntent()) (Java)

    400 Task returns a success response, but FDL data will be empty不*
    接受邀請AppInvite module in Google Play Services invoked when handling intent redirection (from *.page.link or custom domain) 400 Shows a spinner when Google Play Services is invoked and disappears when a 400 response is returned不*

How should I migrate from the service?

We've found that different developers have different needs when it comes to using Firebase Dynamic Links.

Depending on your own use cases and evaluation of your Firebase Dynamic Links usage, it's likely one of the scenarios below will match with your needs.

For this scenario, we recommend you use other deep-linking service providers / vendors, such as Adjust, AppsFlyer, Bitly, Branch, Kochava and other similar providers in the market. (Note, these providers have not been vetted by Google, but do provide similar functionality to Firebase Dynamic Links).

You can also export your deep-link metadata , which can make it easier to migrate your links to whichever provider you choose.

To help find a provider with matching features to Firebase Dynamic Links, refer to the following list of features below.

Firebase Dynamic Links Features:

  • Routes users to the correct store for their device from a single click (and falls back to a webpage if needed)
  • Provides users with a continuation of journey after downloading and installing your app view a deferred deep link
  • Provides users with a contextual experience via deep-linked content in your app (when already installed)
  • Provides analytics data related to dynamic link click events
  • Provides the ability to create short-link URLs
  • Provides the ability to add metadata to links for social sharing

What if I only care about deep-linking to my app after it has already been installed?

For this scenario, we recommend using App Links and Universal Links which are platform-supported ways for developers to provide deep-linking experiences for their users.

Check out this guide for more details on how to migrate to using App Links and Universal Links .

This guide also describes how to optionally use Firebase Hosting to host the necessary domain and asset link verification files on the domain you plan to use for your new links (eg assetlinks.json file for App Links, apple-app-site-association file for Universal Links).

For this scenario, you may not need to take any action in your app to handle the upcoming sunset, however we recommend:

  • Reviewing your existing Firebase Dynamic Links following the guide on exporting your link metadata to ensure your users and app will not be impacted once the links are no longer being served.

  • Deleting your Firebase Dynamic Links URL prefixes in the Firebase console . Note: URL prefix domains will automatically be deleted after August 25th, 2025.

  • Removing the Firebase Dynamic Links SDK from your apps.

If you see a migration scenario that doesn't cover your own needs, please reach out to let us know

The Firebase Dynamic Links APIs for Short Links and Analytics will remain available until the sunset date on August 25th, 2025.

After that date these APIs will no longer be available for use, and the service will be shut down .

Please refer to the guide on exporting your link metadata for instructions on how to export your link metadata.

You can use the export guide to retrieve your Firebase Dynamic Links metadata, which includes the link itself.

You can use the Firebase Dynamic Links Analytics API to retrieve link statistics data for each of your Firebase Dynamic Links. This Analytics API is limited to ~5 QPS. For an example on how to operate within that request limit when using the API, please refer to this Cloud Task sample .

You can also use Google Analytics and export your data for a subset of link analytics data, including App Updates events which are unique to Google Analytics.

If you require a higher request rate to help with your migration, please contact us at Firebase Support .

Your domain and link metadata will be marked for deletion on August 25th, 2025 and purged in accordance with our data retention policy .

Yes, your email link authentication using Firebase Authentication will continue to work.

Firebase Authentication currently uses Firebase Dynamic Links to customize Authentication links, but we will provide an update to ensure that this functionality continues working after the Firebase Dynamic Links service is shut down.

Note that this continuation of functionality is separate from using Firebase Dynamic Links for the primary use cases of store and web routing, deferred and regular deep-linking, which will be deprecated according to the migration timeline shared above.

Please see the "How should I migrate from the service" FAQ which details different migration scenarios and provides migration guides for various alternatives available.