Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When a user verifies their email the metadata is not always updated to reflect the verification status #1948

Closed
samwata opened this issue Nov 13, 2020 · 0 comments
Closed

When a user verifies their email the metadata is not always updated to reflect the verification status #1948

samwata opened this issue Nov 13, 2020 · 0 comments
Assignees
@DavisRayM
Labels
Error Support
Milestone
Week 51-52 (2020)

Comments

@samwata
Copy link
Member

samwata commented Nov 13, 2020 •
edited by imkingrobi
Loading

Environmental Information

Production

Problem description

When a user creates a new account, the verification email is sent to their email and after they have verified their email, the is_email_verified metadata data doesn't get updated.

Steps to reproduce the behavior

  1. Create a new account
  2. Verify the email from the link received
  3. Check your new account if the intercom chatbot is available
@samwata samwata added the Error label Nov 13, 2020
@DavisRayM DavisRayM changed the title When a user creates an acccount their metadata data doesn't get updated hence the intercom chatbot does not appear on the account When a user verifies their email the metadata is not always updated to reflect the verification status Nov 13, 2020
@DavisRayM DavisRayM added this to the Week 47-48 (2020) milestone Nov 13, 2020
@DavisRayM DavisRayM self-assigned this Nov 19, 2020
@DavisRayM DavisRayM mentioned this issue Dec 14, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DavisRayM DavisRayM

Labels
Error Support
Projects
None yet
Milestone
Week 51-52 (2020)
Development

No branches or pull requests
3 participants
@WinnyTroy @samwata @DavisRayM