Skip to content

[HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$500] IOU-After deleting request, hold request system message displayed distorted #40078

Closed

Description

@izarutskaya

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


Version Number: 1.4.62-0
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

  1. Launch app
  2. Tap start chat
  3. Select user with no prior conversation
  4. Tap plus icon and request money without receipt
  5. Again request money with receipt(use camera and upload an image for receipt)
  6. Open 2nd IOU details page
  7. Tap on top 3 dots and select hold request
  8. Enter reason and save it
  9. Tap got it.
  10. Tap 3 dots and select unhold
  11. Again tap 3 dots and delete request

Expected Result:

As in production, user must be navigated to previous IOU details page after deleting 2nd IOU.

Actual Result:

After deleting request, hold request system message displayed section looks distorted. User is in same delete request page in staging with distorted system message section but user navigated to previous IOU details page in production after deleting request.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6445266_1712795995827.zx.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~011ea5b468859985ff
  • Upwork Job ID: 1778348288449794048
  • Last Price Increase: 2024-05-20
  • Automatic offers:
    • dukenv0307 | Reviewer | 102448064
    • ahmedGaber93 | Contributor | 102448065
Issue OwnerCurrent Issue Owner: @anmurali

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 11, 2024
  2. melvin-bot commented on Apr 11, 2024

    @melvin-bot

    Triggered auto assignment to @Gonals (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Apr 11, 2024

    @melvin-bot

    Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  4. github-actions commented on Apr 11, 2024

    @github-actions
    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.
  5. izarutskaya commented on Apr 11, 2024

    @izarutskaya
    Author

    @anmurali I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  6. izarutskaya commented on Apr 11, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #vip-vsb.

  7. izarutskaya commented on Apr 11, 2024

    @izarutskaya
    Author

    Production

    Screen_Recording_20240411_111029_New.Expensify.mp4
  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 11, 2024
  9. 105 remaining items

  10. ahmedGaber93 commented on Jun 21, 2024

    @ahmedGaber93
    Contributor

    @anmurali I think we missed splitting contributor bounty between me and @VincentCorleone based on this #42629 (comment)

  11. melvin-bot commented on Jun 24, 2024

    @melvin-bot

    @anmurali, @Gonals, @ahmedGaber93, @dukenv0307 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  12. anmurali commented on Jun 26, 2024

    @anmurali

    @VincentCorleone - can you pls link me your Upwork profile? I will get you paid out and then close this issue. Sorry, I missed that comment up top.

  13. VincentCorleone commented on Jun 26, 2024

    @VincentCorleone
  14. melvin-bot commented on Jul 1, 2024

    @melvin-bot

    @anmurali, @Gonals, @ahmedGaber93, @dukenv0307 Huh... This is 4 days overdue. Who can take care of this?

  15. melvin-bot commented on Jul 3, 2024

    @melvin-bot

    @anmurali, @Gonals, @ahmedGaber93, @dukenv0307 Still overdue 6 days?! Let's take care of this!

  16. Gonals commented on Jul 5, 2024

    @Gonals
    Contributor

    @anmurali, how's payment going?

  17. melvin-bot commented on Jul 5, 2024

    @melvin-bot

    @anmurali, @Gonals, @ahmedGaber93, @dukenv0307 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  18. anmurali commented on Jul 8, 2024

    @anmurali

    Ah, I paid @VincentCorleone a week ago. Forgot to close the issue.

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

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions