Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Gli SDK di Firebase Authentication offrono un modo semplice per rilevare i vari errori che possono verificarsi con l'utilizzo
metodi di autenticazione. Gli SDK per Flutter mostrano questi errori tramite la classe FirebaseAuthException.
Come minimo, vengono forniti code e message, ma in alcuni casi proprietà aggiuntive come un indirizzo email
e credenziali. Ad esempio, se l'utente sta tentando di accedere con un'email e una password, tutti gli errori generati possono essere rilevati esplicitamente:
try{awaitFirebaseAuth.instance.signInWithEmailAndPassword(email:"barry.allen@example.com",password:"SuperSecretPassword!");}onFirebaseAuthExceptioncatch(e){print('Failed with error code: ${e.code}');print(e.message);}
Ogni metodo fornisce vari codici di errore e messaggi in base al tipo di chiamata di autenticazione. La
L'API di riferimento fornisce dettagli aggiornati sugli errori relativi a ciascun metodo.
Se raggiungi la quota di Firebase Authentication potrebbero essere visualizzati altri errori, ad esempio too-many-requests o operation-not-allowed,
o non aver abilitato un provider di autenticazione specifico.
Gestione degli errori account-exists-with-different-credential
Se hai abilitato l'impostazione Un solo account per indirizzo email nella console di Firebase,
Quando un utente tenta di accedere a un provider (come Google) con un indirizzo email già esistente per il provider di un altro utente Firebase.
(ad esempio Facebook), viene visualizzato l'errore auth/account-exists-with-different-credential insieme a una classe AuthCredential (token ID Google).
Per completare il flusso di accesso al provider previsto, l'utente deve prima accedere al provider esistente (ad es. Facebook) e poi eseguire il collegamento all'altroAuthCredential (token ID di Google).
FirebaseAuthauth=FirebaseAuth.instance;// Create a credential from a Google Sign-in RequestvargoogleAuthCredential=GoogleAuthProvider.credential(accessToken:'xxxx');try{// Attempt to sign in the user in with Googleawaitauth.signInWithCredential(googleAuthCredential);}onFirebaseAuthExceptioncatch(e){if(e.code=='account-exists-with-different-credential'){// The account already exists with a different credentialStringemail=e.email;AuthCredentialpendingCredential=e.credential;// Fetch a list of what sign-in methods exist for the conflicting userList<String>userSignInMethods=awaitauth.fetchSignInMethodsForEmail(email);// If the user has several sign-in methods,// the first method in the list will be the "recommended" method to use.if(userSignInMethods.first=='password'){// Prompt the user to enter their passwordStringpassword='...';// Sign the user in to their account with the passwordUserCredentialuserCredential=awaitauth.signInWithEmailAndPassword(email:email,password:password,);// Link the pending credential with the existing accountawaituserCredential.user.linkWithCredential(pendingCredential);// Success! Go back to your application flowreturngoToApplication();}// Since other providers are now external, you must now sign the user in with another// auth provider, such as Facebook.if(userSignInMethods.first=='facebook.com'){// Create a new Facebook credentialStringaccessToken=awaittriggerFacebookAuthentication();varfacebookAuthCredential=FacebookAuthProvider.credential(accessToken);// Sign the user in with the credentialUserCredentialuserCredential=awaitauth.signInWithCredential(facebookAuthCredential);// Link the pending credential with the existing accountawaituserCredential.user.linkWithCredential(pendingCredential);// Success! Go back to your application flowreturngoToApplication();}// Handle other OAuth providers...}}
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Mancano le informazioni di cui ho bisogno","missingTheInformationINeed","thumb-down"],["Troppo complicato/troppi passaggi","tooComplicatedTooManySteps","thumb-down"],["Obsoleti","outOfDate","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Problema relativo a esempi/codice","samplesCodeIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-07-25 UTC."],[],[],null,["# Error Handling\n\n\u003cbr /\u003e\n\nThe Firebase Authentication SDKs provide a simple way for catching the various errors which may occur which using\nauthentication methods. The SDKs for Flutter expose these errors via the `FirebaseAuthException`\nclass.\n\nAt a minimum, a `code` and `message` are provided, however in some cases additional properties such as an email address\nand credential are also provided. For example, if the user is attempting to sign in with an email and password,\nany errors thrown can be explicitly caught: \n\n try {\n await FirebaseAuth.instance.signInWithEmailAndPassword(\n email: \"barry.allen@example.com\",\n password: \"SuperSecretPassword!\"\n );\n } on FirebaseAuthException catch (e) {\n print('Failed with error code: ${e.code}');\n print(e.message);\n }\n\nEach method provides various error codes and messages depending on the type of authentication invocation type. The\n[Reference API](https://pub.dev/documentation/firebase_auth/latest/) provides up-to-date details on the errors for each method.\n\nOther errors such as `too-many-requests` or `operation-not-allowed` may be thrown if you reach the Firebase Authentication quota,\nor have not enabled a specific auth provider.\n\nHandling `account-exists-with-different-credential` Errors\n----------------------------------------------------------\n\nIf you enabled the One account per email address setting in the [Firebase console](https://console.firebase.google.com/project/_/authentication/providers),\nwhen a user tries to sign in a to a provider (such as Google) with an email that already exists for another Firebase user's provider\n(such as Facebook), the error `auth/account-exists-with-different-credential` is thrown along with an `AuthCredential` class (Google ID token).\nTo complete the sign-in flow to the intended provider, the user has to first sign in to the existing provider (e.g. Facebook) and then link to the former\n`AuthCredential` (Google ID token). \n\n FirebaseAuth auth = FirebaseAuth.instance;\n\n // Create a credential from a Google Sign-in Request\n var googleAuthCredential = GoogleAuthProvider.credential(accessToken: 'xxxx');\n\n try {\n // Attempt to sign in the user in with Google\n await auth.signInWithCredential(googleAuthCredential);\n } on FirebaseAuthException catch (e) {\n if (e.code == 'account-exists-with-different-credential') {\n // The account already exists with a different credential\n String email = e.email;\n AuthCredential pendingCredential = e.credential;\n\n // Fetch a list of what sign-in methods exist for the conflicting user\n List\u003cString\u003e userSignInMethods = await auth.fetchSignInMethodsForEmail(email);\n\n // If the user has several sign-in methods,\n // the first method in the list will be the \"recommended\" method to use.\n if (userSignInMethods.first == 'password') {\n // Prompt the user to enter their password\n String password = '...';\n\n // Sign the user in to their account with the password\n UserCredential userCredential = await auth.signInWithEmailAndPassword(\n email: email,\n password: password,\n );\n\n // Link the pending credential with the existing account\n await userCredential.user.linkWithCredential(pendingCredential);\n\n // Success! Go back to your application flow\n return goToApplication();\n }\n\n // Since other providers are now external, you must now sign the user in with another\n // auth provider, such as Facebook.\n if (userSignInMethods.first == 'facebook.com') {\n // Create a new Facebook credential\n String accessToken = await triggerFacebookAuthentication();\n var facebookAuthCredential = FacebookAuthProvider.credential(accessToken);\n\n // Sign the user in with the credential\n UserCredential userCredential = await auth.signInWithCredential(facebookAuthCredential);\n\n // Link the pending credential with the existing account\n await userCredential.user.linkWithCredential(pendingCredential);\n\n // Success! Go back to your application flow\n return goToApplication();\n }\n\n // Handle other OAuth providers...\n }\n }"]]