[firebase_auth] Exceptions thrown during multi-factor enrolling are not granular enough

[davidmigloz]

When you enroll a new phone for 2fa:

await _firebaseAuth.currentUser!.multiFactor.enroll(
  PhoneMultiFactorGenerator.getAssertion(credential),
  displayName: displayName,
);

or when you resolve the multi factor sign in:

final credential = PhoneAuthProvider.credential(
  verificationId: verificationId,
  smsCode: smsCode,
);
await _multiFactorResolver!.resolveSignIn(PhoneMultiFactorGenerator.getAssertion(credential));

If the SMS verification code is incorrect, the following exception is thrown:

• Code: FirebaseAuthInvalidCredentialsException
• Message: com.google.firebase.auth.FirebaseAuthInvalidCredentialsException: The sms verification code used to create the phone auth credential is invalid. Please resend the verification code sms and be sure use the verification code provided by the user.

If the SMS verification code is expired, the following exception is thrown:

• Code: FirebaseAuthInvalidCredentialsException
• Message: com.google.firebase.auth.FirebaseAuthInvalidCredentialsException: The sms code has expired. Please re-send the verification code to try again.

As you can see, the exception code is the same. So the only way to differentiate them is to check the message, which doesn't sound very robust.

Is is posible to have proper exception wrappers with a unique code?

Thanks.

[davidmigloz]

It seems to be fixed now:

[firebase_auth/invalid-verification-code] The SMS verification code used to create the phone auth credential is invalid. Please resend the verification code sms and be sure to use the verification code provided by the user.