User already exists with a different type of login

Help - Plug n Play
1

Hi team,

I believe I’m experiencing a login method conflict.

I originally signed up for BLESS using my Google account. Later, I logged in using the Email login (passwordless) method. Since then, when I try to log in again via Google, I receive the following error:

“Failed to login – Please refresh the page. User already exists with different type of login.”

I understand BLESS may be using a system like Web3Auth that only allows one unique login method per email. Because both Google and Email login use the same email address, this may have caused a conflict or created two separate accounts.

Could you please:

Help me regain access to my original Google-linked account (which had uptime), and

If needed, remove or unlink the Email login account that was created accidentally?

Thank you for your help. Please let me know if you need any additional details from my side.

2

Thank you for your detailed explanation, Ashfaque! Here’s a summary of your issue for the support team:

Issue Summary

  • Platform/SDK: Web3Auth Plug and Play (PnP) (likely React, based on context)
  • Problem:
    After initially signing up for the BLESS app using Google login, you later logged in using the passwordless Email method (with the same email address). Now, when trying to log in again via Google, you receive the error:

    “Failed to login – Please refresh the page. User already exists with different type of login.”

  • Expected Outcome:
    • Regain access to your original Google-linked account (which had uptime).
    • If needed, remove or unlink the Email login account that was created accidentally.

Additional Context

  • This is a known behavior in Web3Auth where each email is associated with a unique login method. Using the same email with different login methods (e.g., Google vs. passwordless Email) can cause conflicts and may result in separate accounts or login errors.
  • You are requesting account recovery and/or merging/unlinking of the conflicting accounts.

Next Steps

  • The support team may need to coordinate with the BLESS app administrators, as account management (merging or unlinking) is typically handled on the application side, not directly by Web3Auth.
  • If you have any screenshots of the error or additional details (such as the exact email used), please provide them to assist further.

Reference

For more information on this behavior, see:

Support Team Action:

  • Please advise on the process for account recovery in this scenario and whether merging or unlinking is possible from the Web3Auth side, or if the BLESS app team must handle this.

Ashfaque, you don’t need to provide more technical details unless requested. If you have screenshots or the exact email you used, sharing them privately with the support team may help expedite the resolution. Thank you for your patience!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

3

We do not prevent different types of log in from the side of web3auth. Please try the same action on our demo app here https://demo.web3auth.io
It is a custom logic that’s written by Bless folks to prevent login via two different login methods using same emails. Please contact them to remove this restrictions, since it’s not a restriction which Web3Auth imposes on the users.

4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.