Migração do login por link de e-mail do Firebase Dynamic Links (iOS)
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A autenticação do link por e-mail dependia do Firebase Dynamic Links, que será
desativado em 25 de agosto de 2025. Publicamos uma
solução alternativa no SDK do Firebase Authentication para iOS versão 11.8.0+. Se o
app usar Firebase Dynamic Links, migre-o para o novo
sistema baseado em Firebase Hosting.
Migração do domínio associado do Firebase Dynamic Links para um domínio do Firebase Hosting
Em vez de usar um domínio Firebase Dynamic Links, o Firebase Authentication
vai usar o domínio padrão do Firebase Hosting do projeto para criar
links para e-mail e outras ações de links fora da banda em apps para dispositivos móveis. Isso
significa que seu app também precisará ser atualizado para usar esse domínio padrão como
o domínio associado aos links de autenticação de e-mail para o seu app móvel.
Use as instruções a seguir para processar links do novo domínio e instruir o
Firebase Authentication a começar a usar o domínio do Firebase Hosting para
gerar links de apps para dispositivos móveis daqui em diante.
Se você quiser continuar usando qualquer um dos seus domínios
personalizados do Firebase Hosting ou até mesmo o domínio personalizado do Firebase Dynamic Links como seu novo domínio associado,
use as instruções na seção Personalização de links móveis
e adapte as etapas para corresponder ao domínio que você quer usar.
Vincule o domínio do Firebase Hosting ao domínio associado ao app.
Você vai precisar configurar o domínio selecionado como um domínio associado para
links de app. Para configurar o direito de acesso no app, abra a guia
Signing & Capabilities do destino no Xcode e adicione os domínios do Firebase Hosting
da etapa anterior ao recurso "Domínios associados". Se você usar o
domínio padrão do Firebase Hosting, ele será
applinks:PROJECT_ID.firebaseapp.com.
Quando estiver tudo pronto para processar os novos links de domínio, use o
SDK Admin do Firebase para atualizar como você quer que os links de e-mail
sejam gerados e instrua nosso back-end a começar a gerar links usando o novo
domínio Firebase Hosting.
constupdateRequest={mobileLinksConfig:{domain:'HOSTING_DOMAIN'}}constupdateProjectConfig=()=>{projectConfigManager.updateProjectConfig(updateRequest).then((response)=>{// updated project config}).catch((error)=>{console.log('Error updating the project:',error);});}
Envie e resgate o link de e-mail.
Envie o link de login por e-mail como antes. Quando um usuário final clica no link,
ele é redirecionado para o app, se instalado, para concluir o login.
Personalização de links móveis
Você pode usar um domínio Firebase Hosting personalizado ou reutilizar o domínio
Firebase Dynamic Links personalizado como o novo domínio de links para dispositivos móveis.
Reutilize seu domínio personalizado do Firebase Dynamic Links
Você pode reutilizar qualquer um dos seus domínios do Firebase Dynamic Links como domínio
personalizado. No entanto, nenhuma funcionalidade do Firebase Dynamic Links vai ser mais
compatível. Por exemplo, os usuários não poderão ser redirecionados para a app store se o app
não estiver instalado no dispositivo.
[null,null,["Última atualização 2025-08-16 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 iOS SDK version 11.8.0+. If your\napp uses Firebase Dynamic Links, you should migrate your app to the new\nFirebase Hosting based system.\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 on Apple Platforms](/docs/auth/ios/email-link-auth)\nto update your app to use the new automatically provisioned Firebase Hosting\ndefault domain.\n\nUse the following instructions to handle links from the new domain and to\ninstruct Firebase Authentication to start using the Firebase Hosting domain to\ngenerate mobile app links 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 domain,\nusing the instructions in the [Customize Mobile Links](#customize-mobile-links)\nsection, adapt the steps to match the intended domain you'd like to use.\n\n1. **Link Firebase Hosting domain to your app associated domain.**\n\n You'll need to configure the selected domain as an Associated Domain for\n app links. To set up the entitlement in your app, open the target's\n **Signing \\& Capabilities** tab in Xcode and add Firebase Hosting domains\n from the previous step to the Associated Domains capability. If using the\n default Firebase Hosting domain, this will be\n `applinks:`\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e`.firebaseapp.com`.\n\n See [Supporting associated domains](https://developer.apple.com/documentation/xcode/supporting-associated-domains)\n on Apple's documentation site for more information.\n\n An associated domain file has been deployed under all your\n Firebase Hosting domains. To access it, navigate to\n \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e`.firebaseapp.com/.well-known/apple-app-site-association`.\n This AASA file can be overwritten; see\n [Create and host your Universal Links configuration files](/support/guides/app-links-universal-links#create_and_host_your_universal_links_configuration_files_on_your_new_hosting_domain)\n for more information.\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 the\n new Firebase Hosting domain. \n\n const updateRequest = {\n mobileLinksConfig: {\n domain: 'HOSTING_DOMAIN'\n }\n }\n const updateProjectConfig = () =\u003e {\n projectConfigManager.updateProjectConfig(updateRequest)\n .then((response) =\u003e {\n // updated project config\n }).catch((error) =\u003e {\n console.log('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 an end user clicks on the link,\n they will be redirected to the app if installed to finish 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. Link the custom domain to your app associated domain.\n3. [Send an authentication link to the user's email address](/docs/auth/ios/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 the app store if app isn't installed on their device).\n2. [Send an authentication link to the user's email address](/docs/auth/ios/email-link-auth#send_an_authentication_link_to_the_users_email_address) with an updated `ActionCodeSettings` object with a custom domain as `linkDomain`."]]
