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.

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

Login - Focus remains on last digit after login with wrong link and requesting new code #25728

Closed
2 of 6 tasks
lanitochka17 opened this issue Aug 22, 2023 · 7 comments
Closed
2 of 6 tasks
Assignees
Labels
Engineering Reviewing Has a PR in review Weekly KSv2

Comments

@lanitochka17
Copy link

lanitochka17 commented Aug 22, 2023

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


Action Performed:

  1. Open iOS or Android App
  2. On the login screen, enter a new account email
  3. Open the validate email and copy the link
  4. Modify the last part of the link to make 'wrong link'
  5. Navigate to this 'wrong link'
  6. Checked that "Magic code is incorrect" is displayed
  7. Request a new magic link

Expected Result:

Wrong magic code cleared and focus moved to first digit

Actual Result:

Wrong magic code cleared and focus moved to last digit

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.56-8

Reproducible in staging?: Yes

Reproducible in production?: No

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

Bug6173935_T3605918-Android-Invalid-Link-New-Code-Focus.mp4
Bug6173935_T3605918-iOS-Invalid-Link-New-Code-Focus.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Aug 22, 2023
@OSBotify
Copy link
Contributor

👋 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
Copy link

melvin-bot bot commented Aug 22, 2023

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

@roryabraham
Copy link
Contributor

Was able to reproduce this one

@roryabraham
Copy link
Contributor

Not consistently reproducible. Appears to be the result of some race condition maybe?

@roryabraham
Copy link
Contributor

Got a fix

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Hourly KSv2 labels Aug 23, 2023
@roryabraham
Copy link
Contributor

PR is up and ready for review

@roryabraham
Copy link
Contributor

QA'd this and it's fixed on staging by the revert

@roryabraham roryabraham removed the DeployBlockerCash This issue or pull request should block deployment label Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

No branches or pull requests

3 participants