Skip to content

[$500] Request Money - Request money screen opens again on click of Next button #28129

Closed

Description

@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!


Action Performed:

  1. Click on FAB icon
  2. Select Request money option
  3. Enter amount click on Next button
  4. Select user
  5. Click Add to Split
  6. Click on back icon and go to Request money page
  7. Edit amount and click on Next button

Expected Result:

It should navigate to user selection screen

Actual Result:

It navigates to Request money page with a 0 value

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.74.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: Any additional supporting documentation

Screen.Recording.2023-09-25.at.2.41.20.PM.mov
Recording.4746.mp4

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

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~013bcacd63e5609ce5
  • Upwork Job ID: 1706561388369063936
  • Last Price Increase: 2023-12-05

Activity

  1. OSBotify commented on Sep 25, 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.
  2. melvin-bot commented on Sep 25, 2023

    @melvin-bot

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

  3. Pluto0104 commented on Sep 25, 2023

    @Pluto0104
    Contributor

    This isn't a deploy blocker anymore. I can reproduce it on NewDot. It's a regression of #27797.

  4. cristipaval commented on Sep 25, 2023

    @cristipaval
    Contributor

    This is also reproducible in production

  5. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed on Sep 25, 2023
  6. melvin-bot commented on Sep 25, 2023

    @melvin-bot

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

  7. melvin-bot commented on Sep 25, 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
  8. 53 remaining items

  9. FitseTLT commented on Nov 28, 2023

    @FitseTLT
    Contributor

    Isn't this duplicate??

  10. paultsimura commented on Nov 28, 2023

    @paultsimura
    Contributor

    Isn't this duplicate??

    Seems like. But that issue was opened on Oct 10, while this – on Sep 25. According to the rules, that one should be closed in favor of this.

  11. cristipaval commented on Nov 29, 2023

    @cristipaval
    Contributor

    This one needs C+ review, correct?

  12. cristipaval commented on Dec 4, 2023

    @cristipaval
    Contributor

    friendly bump @0xmiroslav

  13. melvin-bot commented on Dec 5, 2023

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  14. cristipaval commented on Dec 7, 2023

    @cristipaval
    Contributor

    bumped @0xmiroslav on Slack here

  15. 0xmiroslav commented on Dec 8, 2023

    @0xmiroslav
    Contributor

    #28618 is merged.
    I am not able to reproduce

  16. cristipaval commented on Dec 8, 2023

    @cristipaval
    Contributor

    alright, thank you @0xmiroslav!

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions