mWeb - Login- Continue button is not clickable after login with link and logout

[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 #19498

Action Performed:

1. Open NewDot on mWeb (Chrome/Android)
2. Login to any account using magic link (not code)
3. Logout
4. Input any email and click continue

Expected Result:

Continue button should be clickable

Actual Result:

Continue button is not clickable

Workaround:

Unknown

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.27.4

Reproducible in staging?: yes

Reproducible in production?: yes

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

Bug6091711_video_35.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - interna Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01730de90b9047f66a
• Upwork Job ID: 1678859166743351296
• Last Price Increase: 2023-07-11

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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

[Christinadobrzyn]

asking if this should be separate - #16301 (comment)

[Christinadobrzyn]

I think this is going to be fixed in the reverted PR here - #16301 (comment)

[Christinadobrzyn]

following - #16301 (comment)

[melvin-bot]

@Christinadobrzyn this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[Christinadobrzyn]

Tracking - #16301 (comment)

[Christinadobrzyn]

Tracking - #16301 (comment)

[Christinadobrzyn]

asking for an update - #16301 (comment)

[melvin-bot]

@Christinadobrzyn this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[Christinadobrzyn]

following the PR here - #16301 (comment)

[Christinadobrzyn]

Following PR here - #20708

[melvin-bot]

@Christinadobrzyn this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01730de90b9047f66a

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @abdulrahuman5196 (Internal)

[abdulrahuman5196]

@Christinadobrzyn Could you provide information on what this issue is? Only C+ is assigned to internal issue?

[Christinadobrzyn]

The internal label was auto-added because this issue is 4 weeks old. I was following this #20708 which just went into production and in my testing, it resolved the issue.

Closing!