Skip to content

[Due for payment 2025-08-01] [$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify #64697

Closed

Description

@mitarachim

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: 9.1.70-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/6326390
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.5 Chrome
App Component: Money Requests

Action Performed:

Preconditions: User A and User B are both gmail accounts, have Wallet enabled (instructions in T6302920). Both users have positive balances in their Wallets (to create a positive balance, send money from the other user)

  1. User A, create a manual expense in 1:1 chat with User B (the amount is less than the wallet balance of User B )
  2. User A, open the expense details and send some messages
  3. User B, navigate to the chat with User A, open the expense details, navigate back to the chat
  4. User B, click "Pay with Expensify" green button on the expense preview

Expected Result:

The app does not crash after paying the expense with Expensify

Actual Result:

The app crashes after user has paid an expense in 1:1 chat with Expensify

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6865862_1750452232272!Pay.txt

Bug6865862_1750452232277.Recording__584.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021937900820992643806
  • Upwork Job ID: 1937900820992643806
  • Last Price Increase: 2025-07-02
Issue OwnerCurrent Issue Owner: @clarajones-expensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 21, 2025
  2. melvin-bot commented on Jun 21, 2025

    @melvin-bot

    Triggered auto assignment to @clarajones-expensify (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.

  3. melvin-bot commented on Jun 24, 2025

    @melvin-bot

    @clarajones-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  4. melvin-bot commented on Jun 25, 2025

    @melvin-bot
  5. changed the title [-]Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/-] [+][$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/+] on Jun 25, 2025
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 25, 2025
  7. melvin-bot commented on Jun 25, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External)

  8. clarajones-expensify commented on Jun 25, 2025

    @clarajones-expensify
    Contributor

    Hi @ahmedGaber93 ! Are you able to repro this issue? Im having trouble doing so. Thanks!

  9. ahmedGaber93 commented on Jun 28, 2025

    @ahmedGaber93
    Contributor

    @clarajones-expensify AFAIK external contributors are not able to set up Wallet, trying to get some help on slack.

  10. 59 remaining items

  11. clarajones-expensify commented on Aug 1, 2025

    @clarajones-expensify
    Contributor

    Hi @ahmedGaber93 ! Would you fill out the above checklist? Thanks!

  12. melvin-bot commented on Aug 1, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@clarajones-expensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1937900820992643806/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. changed the title [-][Due for payment 2025-08-01] [$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/-] [+][Hold for C+ checklist] [Due for payment 2025-08-01] [$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/+] on Aug 1, 2025
  14. clarajones-expensify commented on Aug 1, 2025

    @clarajones-expensify
    Contributor

    Payment Summary

    Upwork Job

    C+: @ahmedGaber93 owed $250 via NewDot
    C: @DylanDylann owed $250 via NewDot

  15. ahmedGaber93 commented on Aug 2, 2025

    @ahmedGaber93
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other: Applause Internal Team
    • [Contributor] 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: N/A. It's a BE case, and I don't have access to this part of the code, but any way it is a minor bug, and we handled the fix in FE.

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    This issue was caught during regression testing, so no need for another one.

  16. ahmedGaber93 commented on Aug 2, 2025

    @ahmedGaber93
    Contributor

    @clarajones-expensify checklist have completed, sorry for the delay 🙏

  17. changed the title [-][Hold for C+ checklist] [Due for payment 2025-08-01] [$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/-] [+][Due for payment 2025-08-01] [$250] Pay with Expensify-The app crashes after user has paid an expense in 1:1 chat with Expensify[/+] on Aug 4, 2025
  18. clarajones-expensify commented on Aug 4, 2025

    @clarajones-expensify
    Contributor
  19. JmillsExpensify commented on Aug 12, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @DylanDylann

  20. quinthar commented on Aug 13, 2025

    @quinthar
    Contributor

    $250 approved for @DylanDylann

  21. trjExpensify commented on Nov 5, 2025

    @trjExpensify
    Contributor

    approved $250 for @ahmedGaber93.

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.DailyKSv2ExternalAdded 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