Memigrasikan login dengan link email dari Firebase Dynamic Links (Android)
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Autentikasi link email sebelumnya mengandalkan Firebase Dynamic Links, yang akan
dinonaktifkan pada 25 Agustus 2025. Kami telah memublikasikan solusi alternatif di Firebase Authentication Android SDK versi 23.2.0+ dan Firebase BoM versi 33.9.0+. Jika aplikasi Anda menggunakan link gaya lama dan Anda ingin menggunakan metode alternatif untuk memigrasikan aplikasi, lihat Melakukan autentikasi dengan Firebase menggunakan Link Email di Android untuk menggunakan sistem berbasis Firebase Hosting yang baru.
Selain itu, jika Anda menggunakan Firebase Authentication Android SDK dengan versi di bawah v20.0.0 (atau
Firebase BoM di bawah v26.0.0) untuk mengelola alur OAuth dengan Firebase Authentication,
Anda harus mengupdate ke versi Authentication SDK atau BoM terbaru
(Authentication v20.0.0+ atau BoM v26.0.0+) untuk terus mengelola alur
OAuth di Firebase Authentication.
Memigrasikan domain Firebase Dynamic Links terkait ke domain Firebase Hosting
Ke depannya, Firebase Authentication akan menggunakan domain default Firebase Hosting untuk project Anda, bukan menggunakan domain Firebase Dynamic Links, untuk membuat link untuk link email dan tindakan link out-of-band lainnya di aplikasi seluler. Artinya, aplikasi Anda juga perlu diupdate untuk menggunakan domain default ini sebagai domain terkait untuk link autentikasi email ke aplikasi seluler Anda.
Gunakan petunjuk berikut untuk menangani link dari domain baru dan untuk
memberi tahu Firebase Authentication agar mulai menggunakan domain baru untuk membuat link
aplikasi seluler ke depannya.
Jika Anda ingin terus menggunakan domain Firebase Hosting kustom atau bahkan domain Firebase Dynamic Links kustom sebagai domain terkait baru, ikuti langkah-langkah yang cocok dengan domain yang ingin Anda gunakan. Perhatikan
bahwa setelah menyelesaikan petunjuk di bagian berikut, fitur deep
linking di domain kustom Firebase Dynamic Links Anda akan dihapus;
hanya domain itu sendiri yang akan tetap ada untuk membuat link email.
Mengonfigurasi aplikasi Android untuk menangani link Firebase Hosting
Untuk menangani link ini dari aplikasi Android, Anda harus menentukan nama paket aplikasi di setelan project Firebase console. Selain itu, SHA-1 dan SHA-256 sertifikat aplikasi harus dimasukkan.
Jika ingin link Firebase Hosting ini dialihkan ke aktivitas
tertentu, Anda harus mengonfigurasi filter intent di
file AndroidManifest.xml. Filter intent harus menangkap Firebase Hosting link domain Anda. Di AndroidManifest.xml:
Saat pengguna membuka link hosting dengan jalur "/__/auth/links" serta
skema dan host yang Anda tentukan, aplikasi Anda akan memulai aktivitas dengan
filter intent ini untuk menangani link tersebut.
Mengonfigurasi project untuk menggunakan link baru
Jika sudah siap menangani link domain baru, Anda dapat menggunakan Firebase Admin SDK untuk memperbarui cara dalam pembuatan link email dan menginstruksikan backend kami untuk mulai membuat link menggunakan domain Firebase Hosting baru.
import{getAuth}from'firebase-admin/auth';constupdateEmailAuthDomain=async()=>{constupdateRequest={mobileLinksConfig:{domain:'HOSTING_DOMAIN',},};constprojectConfigManager=getAuth().projectConfigManager();try{constresponse=awaitprojectConfigManager.updateProjectConfig(updateRequest);// Updated project configconsole.log('Project configuration updated successfully:',response);}catch(error){console.error('Error updating the project:',error);}};
Mengirim dan menukarkan link email
Kirim link login email seperti sebelumnya. Saat pengguna akhir mengklik link,
mereka akan dialihkan ke aplikasi jika sudah diinstal untuk menyelesaikan login.
Menyesuaikan link seluler
Anda dapat menggunakan domain Firebase Hosting kustom atau menggunakan kembali domain
Firebase Dynamic Links kustom sebagai domain link seluler baru.
Menggunakan kembali domain Firebase Dynamic Links kustom
Anda dapat menggunakan kembali domain Firebase Dynamic Links sebagai domain kustom. Namun, semua fungsi Firebase Dynamic Links tidak akan lagi
didukung (misalnya, pengguna tidak dapat dialihkan ke app store jika
aplikasi tidak diinstal di perangkat mereka).
Konfigurasikan aplikasi Android untuk menangani link Firebase Hosting
(petunjuk di bagian sebelumnya di atas).
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[],[],null,["Email link authentication previously relied on Firebase Dynamic Links, which will be\n[shut down on August 25, 2025](/support/dynamic-links-faq). We've published an\nalternative solution in the Firebase Authentication Android SDK version 23.2.0+ and\nFirebase BoM version 33.9.0+. If your app uses the old style links and you\nwant to use an alternative method for migrating your app, see\n[Authenticate with Firebase using Email Link in Android](/docs/auth/android/email-link-auth)\nto use the new Firebase Hosting based system.\n\nAlso, if you're using the **Firebase Authentication Android SDK below v20.0.0 (or the\nFirebase BoM below v26.0.0) to manage OAuth flows** with Firebase Authentication,\nyou'll need to update to the latest Authentication SDK or BoM version\n(Authentication v20.0.0+ or BoM v26.0.0+) in order to continue managing OAuth\nflows in Firebase Authentication.\n\nMigrate your associated Firebase Dynamic Links domain to a Firebase Hosting domain\n\nMoving forward, rather than using a Firebase Dynamic Links domain, Firebase Authentication\nwill use the Firebase Hosting default domain for your project to create\nlinks for email link and other out-of-band link actions in mobile apps. This\nmeans that your app will also need to be updated to use this default domain as\nthe associated domain for email authentication links to your mobile app.\n\nYou can follow the instructions in\n[Authenticate with Firebase Using Email Link in Android](/docs/auth/android/email-link-auth) to update your mobile app links\nto use the new automatically provisioned Firebase Hosting default domain.\n\nUse the following instructions to handle links from the new domain and to\ninstruct Firebase Authentication to start using the new domain to generate mobile app\nlinks going forward.\n\nIf you'd like to continue using any of your custom Firebase Hosting domains\nor even your custom Firebase Dynamic Links domain to be your new associated\ndomain, follow the steps that match the intended domain you'd like to use. Note\nthat after completing the instructions in the following section, the deep\nlinking feature on your Firebase Dynamic Links custom domain will be removed;\nonly the domain itself will remain for creating email links.\n\n1. **Configure your Android application to handle your Firebase Hosting link**\n\n 1. In order to handle these links from your Android application, your app's package name needs to be specified in the Firebase console project settings. In addition, the SHA-1 and SHA-256 of the application certificate need to be provided.\n 2. If you want these Firebase Hosting links to redirect to a specific\n activity, you will need to configure an intent filter in your\n `AndroidManifest.xml` file. The intent filter should catch\n Firebase Hosting links of your domain. In `AndroidManifest.xml`:\n\n \u003cintent-filter android:autoVerify=\"true\"\u003e\n \u003caction android:name=\"android.intent.action.VIEW\" /\u003e\n \u003ccategory android:name=\"android.intent.category.BROWSABLE\" /\u003e\n \u003ccategory android:name=\"android.intent.category.DEFAULT\" /\u003e\n \u003cdata\n android:scheme=\"https\"\n android:host=\"PROJECT_ID.firebaseapp.com or a custom hosting domain\"\n android:pathPrefix=\"/__/auth/links\" /\u003e\n \u003c/intent-filter\u003e\n\n When users open a hosting link with the \"/__/auth/links\" path and the\n scheme and host you specify, your app will start the activity with this\n intent filter to handle the link.\n | **Important:** To ensure a seamless rollback, we recommend keeping your existing intent filter that handles Firebase Dynamic Links while trying out the Firebase Hosting link solution. The Firebase Dynamic Links solution will be available until August 25, 2025.\n2. **Configure your project to use the new links**\n\n When you're ready to handle the new domain links, you can use the\n [Firebase Admin SDK](/docs/admin/setup) to update how you want email links\n to be generated and instruct our backend to start generating links using\n the new Firebase Hosting domain. \n\n import { getAuth } from 'firebase-admin/auth';\n\n const updateEmailAuthDomain = async () =\u003e {\n const updateRequest = {\n mobileLinksConfig: {\n domain: 'HOSTING_DOMAIN',\n },\n };\n\n const projectConfigManager = getAuth().projectConfigManager();\n\n try {\n const response = await projectConfigManager.updateProjectConfig(updateRequest);\n // Updated project config\n console.log('Project configuration updated successfully:', response);\n } catch (error) {\n console.error('Error updating the project:', error);\n }\n };\n\n | **Important:** To rollback to the Firebase Dynamic Links while implementing and testing the backup solution, you should set the domain back to `FIREBASE_DYNAMIC_LINK`. The Firebase Dynamic Links solution will be available until August 25, 2025.\n3. **Send and redeem the email link**\n\n Send the email sign-in link as before. When the end user clicks the link,\n they will be redirected to the app if installed to complete the sign-in.\n\nCustomize your mobile links\n\nYou can use a custom Firebase Hosting domain or reuse your custom\nFirebase Dynamic Links domain to be your new mobile links domain.\n\nUse a custom Firebase Hosting domain\n\n1. Follow the [Firebase Hosting guide](/docs/hosting/custom-domain) to set up a custom domain.\n2. Configure your Android application to handle your Firebase Hosting link. (instructions in previous section above).\n3. [Send an authentication link to the user's email\n address](/docs/auth/android/email-link-auth#send_an_authentication_link_to_the_users_email_address) with an updated `ActionCodeSettings` object with a custom domain as `linkDomain`.\n\nRe-use your custom Firebase Dynamic Links domain\n\n1. You can re-use any of your Firebase Dynamic Links domains as your custom domain. However, any Firebase Dynamic Links functionality will no longer be supported (for example, users cannot be redirected to an app store if the app isn't installed on their device).\n2. Configure your Android application to handle your Firebase Hosting link (instructions in previous section above).\n3. [Send an authentication link to the user's email\n address](/docs/auth/android/email-link-auth#send_an_authentication_link_to_the_users_email_address) with an updated `ActionCodeSettings` object with a custom domain as `linkDomain`."]]
