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
[HOLD for payment 2024-07-17][$250] Expense - App crashes when opening an expense report after submitting another expense #44960
Version Number: 9.0.5-2 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Action Performed:
Sign in to an account
Go to FAB > submit expense > Manual expense
Enter an amount
Select a user you have never submitted an expense to
Submit the expense
Navigate to the chat with the user you just submitted the expense to
Click on the "+" icon
Click on submit expense > Manual expense > Enter amount >Next > Submit
Go to the combined expense report and open the first expense you submitted
Expected Result:
The expense report opens and the app does not crash
Actual Result:
App crashes after opening the report
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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:
Identify the pull request that introduced this issue and revert it.
@rlinoz FYI 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
It looks like we are creating the first money request in a different policyID other than _FAKE_, and when we open that report again we set it back to fake, which then crashes. Looking like a backend bug.
Yeah, tested with the production Web-E branch and still happens in dev, so I am gonna go ahead and remove the DeployBlocker for Web-E, will continue looking after lunch.
Thx @brunovjk , that's weird that the fee isn't removed too, hmmm...
How has the 10% fee been debited if it takes them 5 days to pay? Do you have any screenshots you can share.
Currently, all contributors need to be paid via Upwork for 18 months from their first hire, unfortunately you have a while. 2025-08-09 Bruno Rocha
Thx @brunovjk , that's weird that the fee isn't removed too, hmmm... How has the 10% fee been debited if it takes them 5 days to pay? Do you have any screenshots you can share.
It shows that the fee was removed, I tried refund anyway, can you confirm if everything went well?
Currently, all contributors need to be paid via Upwork for 18 months from their first hire, unfortunately you have a while. 2025-08-09 Bruno Rocha
Thank you very much @mallenexpensify for the information!!!! I'll leave a note here, it goes quickly :D
@isabelastisser when you pay contributors can you provide more detail in the description so that we know who's getting paid where, and how much? Thx.
@allroundexperts plz complete the BZ checklist below, seems like we'd want a regression test for this, right?
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:
[@] 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:
[@] 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.
[@bz] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Jul 8, 2024
Triggered auto assignment to @rlinoz (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 8, 2024
👋 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:
lanitochka17 commentedon Jul 8, 2024
@rlinoz FYI 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
Julesssss commentedon Jul 8, 2024
Crash seems to be related to Policy key changing? Are we temporarily setting it to FAKE
rlinoz commentedon Jul 8, 2024
Taking a look at this, weird one
rlinoz commentedon Jul 8, 2024
It looks like we are creating the first money request in a different policyID other than
_FAKE_, and when we open that report again we set it back to fake, which then crashes. Looking like a backend bug.rlinoz commentedon Jul 8, 2024
not happening in prod though, and apparently we didn't deploy anything related to staging in Web-E
Julesssss commentedon Jul 8, 2024
Hmm, nice. At least it points back to app.
I wonder if any of the PRs seem associated with policies. Does this issue seem related?
Julesssss commentedon Jul 8, 2024
Oops lol, ignore that 🤦
rlinoz commentedon Jul 8, 2024
Yeah, tested with the production Web-E branch and still happens in dev, so I am gonna go ahead and remove the DeployBlocker for Web-E, will continue looking after lunch.
40 remaining items
mallenexpensify commentedon Jul 20, 2024
Thx @brunovjk , that's weird that the fee isn't removed too, hmmm...
How has the 10% fee been debited if it takes them 5 days to pay? Do you have any screenshots you can share.
Currently, all contributors need to be paid via Upwork for 18 months from their first hire, unfortunately you have a while. 2025-08-09 Bruno Rocha
brunovjk commentedon Jul 20, 2024
It shows that the fee was removed, I tried refund anyway, can you confirm if everything went well?
Thank you very much @mallenexpensify for the information!!!! I'll leave a note here, it goes quickly :D
mallenexpensify commentedon Jul 22, 2024
Yup, confirming we got the refund. Thanks @brunovjk , I know it's a bit of a pain. Luckily it happens pretty rarely.
Contributor: @nkdengineer paid $250 via Upwork
Contributor+: @allroundexperts owed $250 via NewDot.
@isabelastisser when you pay contributors can you provide more detail in the description so that we know who's getting paid where, and how much? Thx.
@allroundexperts plz complete the BZ checklist below, seems like we'd want a regression test for this, right?
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:
melvin-bot commentedon Jul 23, 2024
@rlinoz, @allroundexperts, @isabelastisser, @nkdengineer Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
rlinoz commentedon Jul 24, 2024
friendly bump @allroundexperts
allroundexperts commentedon Jul 29, 2024
Checklist
Regression test
Verify that the expense report opens and the app does not crash
Do we 👍 or 👎 ?
isabelastisser commentedon Jul 29, 2024
Sorry for the confusion, team! And thanks for handling this, @mallenexpensify!
@rlinoz, can you please review the regression test above? Thanks!
rlinoz commentedon Jul 29, 2024
I think since this was caught during regression testing we can skip creating a new one.
isabelastisser commentedon Jul 29, 2024
Sounds good, thanks @rlinoz!
This is all set, closing!
JmillsExpensify commentedon Aug 21, 2024
$250 approved for @allroundexperts