You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[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
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)
User A, create a manual expense in 1:1 chat with User B (the amount is less than the wallet balance of User B )
User A, open the expense details and send some messages
User B, navigate to the chat with User A, open the expense details, navigate back to the chat
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
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
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
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.
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
Activity
melvin-bot commentedon Jun 21, 2025
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.melvin-bot commentedon Jun 24, 2025
@clarajones-expensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 25, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021937900820992643806
[-]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[/+]melvin-bot commentedon Jun 25, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (
External)clarajones-expensify commentedon Jun 25, 2025
Hi @ahmedGaber93 ! Are you able to repro this issue? Im having trouble doing so. Thanks!
ahmedGaber93 commentedon Jun 28, 2025
@clarajones-expensify AFAIK external contributors are not able to set up Wallet, trying to get some help on slack.
59 remaining items
clarajones-expensify commentedon Aug 1, 2025
Hi @ahmedGaber93 ! Would you fill out the above checklist? Thanks!
melvin-bot commentedon Aug 1, 2025
Payment Summary
Upwork Job
BugZero Checklist (@clarajones-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[/-][+][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[/+]clarajones-expensify commentedon Aug 1, 2025
Payment Summary
Upwork Job
C+: @ahmedGaber93 owed $250 via NewDot
C: @DylanDylann owed $250 via NewDot
ahmedGaber93 commentedon Aug 2, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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.
ahmedGaber93 commentedon Aug 2, 2025
@clarajones-expensify checklist have completed, sorry for the delay 🙏
[-][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[/+]clarajones-expensify commentedon Aug 4, 2025
Good to go
JmillsExpensify commentedon Aug 12, 2025
$250 approved for @DylanDylann
quinthar commentedon Aug 13, 2025
$250 approved for @DylanDylann
trjExpensify commentedon Nov 5, 2025
approved $250 for @ahmedGaber93.