Email not shown for new user in the contact method (on Profile page)

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Go to staging dot on web chrome and login with a new user -create a new account (important step)
2. Click on Settings > Profile
3. You're on the Profile page and notice that on 'Contact method' that is just present below the 'Display name' doesn't shown the email
4. Follow the same steps on production with a new user and notice that on the Profile page, email is shown as default under 'Contact method'

Expected Result:

Email should be shown for new user in the contact method (on Profile page)

Actual Result:

Email not shown for new user in the contact method (on Profile page) in staging but works well on production

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.29-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

green-2023-06-19_11.55.10.mp4

Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687155411925429

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[luacmartins]

This had the same root cause of #fireroom-getpersonaldetailslist and it's no longer reproducible after the latest Auth deploy. Closing.

[priya-zha]

@luacmartins It's still reproducible on staging. Can you please check it once more?

[luacmartins]

Just tried again with a brand new account and still can't reproduce

Screen.Recording.2023-06-20.at.9.26.25.AM.mov

[priya-zha]

It seems weird that I'm still able to reproduce it. Also the same issue was posted by some other contributor today here :. I tried this on chrome web with a gmail account. I don't know whether it's related or not , but have you tried with a gmail account? Thanks

green-2023-06-20_21.55.20.mp4

[luacmartins]

Just tried with a new gmail account and I still can't reproduce the issue.