[firebase_auth: ^5.3.4]: verifyBeforeUpdateEmail(newEmail) isn't checking whether newEmail is already registered.

[Kamran73]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Auth

Which platforms are affected?

No response

Description

Firebase_auth introduced a new function {verifyBeforeUpdateEmail(newEmail)} for updating email.

issue: if new email Is already used/registered, verifyBeforeUpdateEmail(newEmail) doesn't throw any exception but returns with a success response with no verification link sent to new email address.

• I tried it with firebase emulator and it works fine, it throws exception that "Email already used, go to login".

Reproducing the issue

package:
firebase_auth: ^5.3.4

1. register a user with any email e.g [email protected] ----> 1st user

2. register and login another user with new email e.g [email protected] ---- 2nd user

3. try to update 2nd user email using FirebaseAuth.instance.currentUser.verifyBeforeUpdateEmail('[email protected]');

expected response: exception ('email already used go to login')
actual response: success but no link sent to '[email protected]'

Firebase Core version

3.8.1

Flutter Version

3.24.0

Relevant Log Output

Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

[SelaseKay]

Hi @Kamran73, thanks for the report. However, I'm unable to reproduce this issue on android and iOS. Could you provide a sample minimal code reproducing this issue? Also, what platform(iOS, android, web, etc) are you experiencing this issue on?

[Kamran73]

@SelaseKay I provided a sample code above, but I am pasting it again. This is just one line of code to reproduce the issue.

Platform I am testing on is Android.

code:
await FirebaseAuth.instance.currentUser!.verifyBeforeUpdateEmail('[email protected]');

[SelaseKay]

Hi @Kamran73, I'm unable to reproduce this issue. It seems to work as expected on my end. Could you provide a complete minimal repository reproducing this issue?