-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Email verification #5465
Comments
@rnehrboss This happens because it "preloads" the link, which automatically verifies the email. I'll fix this by adding a confirmation step with a button |
Thanks @berry-13 . I appreciate it. I'm suprised that more people havent mentioned it. |
I was the one who worked on this, and during testing with Gmail and Chrome on an iPad, I didn't encounter any issues. However, I haven't tested it since, as I don't frequently use Apple products. It's possible that this issue affected only iOS/iPadOS users with Safari and Chrome, or those using Outlook emails. I've now thought an even better solution, which I'll explain in detail in the PR |
@berry-13 Wow.. quick work. Thanks. Thanks again? |
uh oh.. i think I blew it. @berry-13 I put your changed code over the AuthService.js and VerifyEmail.tsx, rebuilt, but now get: LibreChat | Node.js v20.18.2 Any thoughts? |
@rnehrboss No need to build the image; just pull the latest image, and the fix will be in it. Make sure to first pull the latest image, then recreate the Docker container so it uses the new image. Afterward, delete the old image |
What happened?
When setting up new account, and clicking on the email verification, it seems that both Safari and Chrome, on IOS bring up a page that says "Email Verification Failed"
However, it looks from the user database that LibreChat is setting the emailVerified in the User collection record to "true". It confuses users because they think it didn't work.
Steps to Reproduce
Sign up new account.
Click verify email.
What browsers are you seeing the problem on?
No response
Relevant log output
Screenshots
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: