Skip to content

Legal last name field gives error when clicking on the save btn, but don't give us an error when click on and out of it #24218

Closed

Description

@kavimuru

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 website and Settings > Profile > Personal details > Legal name
  2. When you click on and out of the dirst field you are given an error but not given with second field. But there is error for second field when clicking on the save btn

Expected Result:

Legal last name field should give us an error when click on and out of it

Actual Result:

Legal last name field gives error when clicking on the save btn, but don't give us an error when click on and out of it

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.50-0
Reproducible in staging?: y
Reproducible in production?: y
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

Recording.5754.mp4
screen-capture.71.webm

Expensify/Expensify Issue URL:
Issue reported by: @MahmudjonToraqulov
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690889073145779

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 7, 2023
  2. melvin-bot commented on Aug 7, 2023

    @melvin-bot

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

  3. melvin-bot commented on Aug 7, 2023

    @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
  4. hungvu193 commented on Aug 7, 2023

    @hungvu193
    Contributor

    Correct me if I'm wrong, but I feel like this is another regressions from this #21838

  5. lschurr commented on Aug 7, 2023

    @lschurr
    Contributor

    @eVoloshchak @techievivek - Do you agree this is a regression and should be placed on hold?

  6. techievivek commented on Aug 8, 2023

    @techievivek
    Contributor

    Yes, this looks like a regression from the PR #23306 @joh42 @eVoloshchak), I think we can put this on HOLD for now.

  7. chiragxarora commented on Aug 8, 2023

    @chiragxarora
    Contributor

    This is basically duplicate, same error can be seen on all the forms, we should close all of these except the oldest resport.

    Bug: error on blurring present only on first field which has autofocus, not the others

    Or we could go on creating GHs for all the forms

  8. lschurr commented on Aug 8, 2023

    @lschurr
    Contributor

    Cool. Should we close or just put on hold?

  9. techievivek commented on Aug 10, 2023

    @techievivek
    Contributor

    We have reverted the original fix #21838 (comment) so we can close this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions