Skip to content

[HOLD for payment 2023-08-28] [$500] Request money - The app crashes when user deleted the request money #25451

Closed

Description

@lanitochka17

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. Launch app
  2. Tap Fab
  3. Tap request money
  4. Tap enter any amount
  5. Tap next
  6. Select any user
  7. Tap Request money
  8. Tap last transaction to open the last requested money page
  9. Tap the money requested
  10. In IOU details page, tap 3 dots to select "delete request"
  11. Tap delete request

Expected Result:

The request money should be deleted

Actual Result:

The app crashes when user deleted the request money

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.55-1

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

Bug6168801_new_crash.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Ingernal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01b8ef599b7ac8134d
  • Upwork Job ID: 1692480853057089536
  • Last Price Increase: 2023-08-18
  • Automatic offers:
    • abdulrahuman5196 | Reviewer | 26194635
    • pradeepmdk | Contributor | 26194639

Activity

  1. OSBotify commented on Aug 18, 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 Aug 18, 2023

    @melvin-bot

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

  3. pradeepmdk commented on Aug 18, 2023

    @pradeepmdk
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    [Request money - The app crashes when the user deleted the request money]

    What is the root cause of that problem?

    Screenshot 2023-08-18 at 10 22 17 AM
    after delete request title is 0 here 0 is number

    accessibilityLabel={props.title}

    this PR add this https://github.com/Expensify/App/pull/20251/files accessibilityLabel

    What changes do you think we should make in order to solve the problem?

    we need fix the type to string here accessibilityLabel
    possiblity to get title is null or undefined

                        accessibilityLabel={props.title ? props.title.toString() : ''}

    we need fix below those as well. all should be an type error only.
    Screenshot 2023-08-18 at 10 30 38 AM
    Screenshot 2023-08-18 at 10 30 53 AM

    result

    Screen.Recording.2023-08-18.at.10.35.57.AM.mov
  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Aug 18, 2023
  5. changed the title [-]Request money - The app crashes when user deleted the request money[/-] [+][$1000] Request money - The app crashes when user deleted the request money[/+] on Aug 18, 2023
  6. melvin-bot commented on Aug 18, 2023

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Aug 18, 2023
  8. melvin-bot commented on Aug 18, 2023

    @melvin-bot

    Triggered auto assignment to @flaviadefaria (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  9. 45 remaining items

  10. melvin-bot commented on Aug 21, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2023-08-28. 🎊

    After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    For reference, here are some details about the assignees on this issue:

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  11. melvin-bot commented on Aug 21, 2023

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@abdulrahuman5196] The PR that introduced the bug has been identified. Link to the PR:
    • [@abdulrahuman5196] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@abdulrahuman5196] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@abdulrahuman5196] Determine if we should create a regression test for this bug.
    • [@abdulrahuman5196] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@alexpensify / @flaviadefaria] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  12. alexpensify commented on Aug 28, 2023

    @alexpensify
    Contributor

    I'm catching up from being OOO, I will prepare the payment steps.

  13. alexpensify commented on Aug 30, 2023

    @alexpensify
    Contributor

    Here is the payment summary:

    • External issue reporter - N/A
    • Contributor that fixed the issue - @pradeepmdk $750
    • Contributor+ that helped on the issue and/or PR - @abdulrahuman5196 $750

    Upwork Job: https://www.upwork.com/jobs/~01b8ef599b7ac8134d

    *If applicable, the bonuses will be applied on the final payment

    Extra Notes regarding payment: The amount is less per @mountiny's feedback here but there is an urgency bonus. I'm calculating half of the base amount of $500 equals $250, so the final amount given would be $750.

    Let me know if there is any feedback or else I will complete the payment tomorrow. Thanks!

  14. alexpensify commented on Aug 30, 2023

    @alexpensify
    Contributor

    Everyone has been paid in Upwork. @abdulrahuman5196 please complete the checklist and we can close ou this GH. Thanks!

  15. alexpensify commented on Sep 1, 2023

    @alexpensify
    Contributor

    @abdulrahuman5196 - we are waiting to close this GH until the checklist is complete, can we get an update soon? Thanks!

  16. abdulrahuman5196 commented on Sep 4, 2023

    @abdulrahuman5196
    Contributor

    The PR that introduced the bug has been identified. Link to the PR:
    The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

    https://github.com/Expensify/App/pull/20251/files#r1314735902

    Determine if we should create a regression test for this bug.
    If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

    No. This is a minor fix and won't be beneficial to add regression test case.

    @alexpensify Sorry for the delay. Completed the checklist

  17. alexpensify commented on Sep 4, 2023

    @alexpensify
    Contributor

    Thanks! I'm going to close now-- great work team.

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions