Following up on this topic, we haven’t identified the root cause yet. Could you please check using the Firebase UID 54gXma2B7FRDLuLNTryNPc9rRCJ3?
Thanks for following up, Felipe! I see you’re referencing the Plug n Play SDK and continuing the discussion from your previous topic about the wallet address change issue. You’ve also provided the Firebase UID: 54gXma2B7FRDLuLNTryNPc9rRCJ3.
To help the support team investigate further, could you please share:
- The specific initialization and login code snippets you’re using with Plug n Play?
- Any relevant browser console logs or screenshots showing the issue (if applicable)?
- If you’re using custom authentication (e.g., a custom verifier or your own authentication backend), please provide the verifier name and method of login.
This information will help us pinpoint the root cause more efficiently. In the meantime, if you haven’t already, please review the Plug n Play troubleshooting guide for common issues.
Let us know if you can provide those details, and we’ll make sure this gets the attention it needs!
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