[HOLD for payment 2023-05-02] [$1000] Secondary login - Red dot stays after adding email with Expensify account

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #15330

Action Performed:

1. Go https://staging.new.expensify.com/
   and login
2. Go to profile
3. Add as secondary login an email that has expensify account (or that was added to another account as secondary login)
4. Error message is displayed with red dot
5. Click X to dismiss the error

Expected Result:

Red dot should disappear across the app

Actual Result:

Red Dot stays for some time

Workaround:

Unknown

Platforms:

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

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

Version Number: 1.2.99.3

Reproducible in staging?: Yes

Reproducible in production?: New feature

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

Bug6014995_video_82.mp4

Expensify/Expensify Issue URL:

Issue reported by: @Natnael-Guchima & Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013e2ea9daf6a5597b
• Upwork Job ID: 1648326062248083456
• Last Price Increase: 2023-04-18

[MelvinBot]

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

[MelvinBot]

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

[miljakljajic]

Reproducible for me:

[miljakljajic]

Going to spin the wheel on this again as I am OOO next week.

[MelvinBot]

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