[Firebase_Auth] Re-authenticate with credential returns platform exception.

[OliverNarramore]

If I use a hypothetical user to re-authenticate,

AuthCredential credential = EmailAuthProvider.getCredential(
        email: "test@test.com", password: "password" );

and then pass this credential to:

 user.reauthenticateWithCredential(credential)
      .whenComplete(() async {
print('complete');
 })
.catchError((e) {
        print(e);
      });

where user was retrieved previously (user = await _auth.currentUser();)

The request returns:

I/BiChannelGoogleApi( 6616): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzao@64242b7
I/flutter ( 6616): completed
I/flutter ( 6616): PlatformException(FirebaseException, An internal error has occurred. [ 7: ], null)

[BondarenkoStas]

@OliverNarramore do you have any firewall settings? Just checking if it's similar with #290.

[a-leblond]

Hi,

I'm getting a similar error on both the emulator and my own device (Pixel 3XL).

Here is the code :

Future<bool> changePassword(String oldPassword, String newPassword) async {
try {
      FirebaseUser user = await _firebaseAuth.currentUser();
      String email = user.email;
      AuthResult result = await user.reauthenticateWithCredential(
        EmailAuthProvider.getCredential(email: email, password: oldPassword)
      );
      await result.user.updatePassword(newPassword);
      return true;
    } catch(error) {
      print(error);
      return false;
    }
  }

And here is the output :

W/BiChannelGoogleApi(11840): [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzak@7ca1ced
D/FirebaseAuth(11840): Notifying id token listeners about user ( yxS6TtOfHnTHL5uNDbGU4q4kRRs2 ).
I/flutter (11840): NoSuchMethodError: The method '[]' was called on null.
I/flutter (11840): Receiver: null
I/flutter (11840): Tried calling: []("user")

My Pixel is connected to the cellular network while the emulator is on a private Wi-Fi.

[kirstywilliams]

This should have been fixed with PR-237. Closing as resolved. If you are still experiencing issues please open a new issue with concise steps to reproduce.