Skip to content

App crash on entering test amount on Test transaction page #14847

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. Go to any workspace
  2. Connect bank manually
  3. Select “Manually enter account details” and enter Routing number 011401533 and Account number 1111222233331111
  4. Company Info - enter random info but complete all fields. You will fail once and get asked to double check information. Select “Save & Continue” again
  5. Personal Info - use any test data. For last 4 SSN use 3333.
  6. Beneficial Owners:
  • Toggle terms and conditions
  • Toggle confirmation that the information provided is true and accurate
  1. Enter amount in test transaction page

Expected Result:

App doesn’t crash

Actual Result:

App crash with console error - amount.trim is not a function at ValidationStep.filterInput

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: v1.2.65-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:

Screen.Recording.2023-02-04.at.2.21.29.AM.1.mov
Recording.1448.mp4

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

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 6, 2023
  2. locked and limited conversation to collaborators on Feb 6, 2023
  3. unlocked this conversation on Feb 6, 2023
  4. melvin-bot commented on Feb 6, 2023

    @melvin-bot

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

  5. locked and limited conversation to collaborators on Feb 6, 2023
  6. melvin-bot commented on Feb 6, 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
  7. unlocked this conversation on Feb 6, 2023
  8. locked and limited conversation to collaborators on Feb 6, 2023
  9. OSBotify commented on Feb 6, 2023

    @OSBotify
    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.
  10. 27 remaining items

  11. changed the title [-][HOLD for payment 2023-02-14] [HOLD for payment 2023-02-13] App crash on entering test amount on Test transaction page[/-] [+]App crash on entering test amount on Test transaction page[/+] on Feb 8, 2023
  12. robertjchen commented on Feb 8, 2023

    @robertjchen
    Contributor

    re: BugZero checklist

    This code existed 20 months ago in #3587 so it probably wasn't the cause, the next place to look at would be TextInput, BaseTextInput, and Form (which calls the validation) but nothing really stands out other than some recent styling changes. 🤔

    The base react-native component returns a pure string, so somewhere along the line some type inference happens and we get a numeric type.

    Either way, we'll probably have to do some git bisects to find the cause- given the limited scope, I don't think we should sink too much time into it beyond this. We can create a dedicated issue to hunt this down if it happens again- going to close this out for now.

  13. rushatgabhane commented on Feb 8, 2023

    @rushatgabhane
    Member

    @robertjchen @mateocole can you please re-open the issue for reporting bonus? Thanks

  14. robertjchen commented on Feb 9, 2023

    @robertjchen
    Contributor

    Ah, my bad I forgot- re-opened!

  15. mateocole commented on Feb 14, 2023

    @mateocole
  16. mateocole commented on Feb 16, 2023

    @mateocole

    sry forgot to tag you @rushatgabhane

  17. robertjchen commented on Feb 17, 2023

    @robertjchen
    Contributor

    Looks like this is all set!

  18. rushatgabhane commented on Feb 17, 2023

    @rushatgabhane
    Member

    @robertjchen @mateocole reporting bonus is left. please reopen

  19. mateocole commented on Feb 17, 2023

    @mateocole

    @rushatgabhane all paid, apologies for the confusion i sent you a separate offer and withdrew it, but paid the contract in the link above!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions