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-06-02] [$250] Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id #61573
Version Number: V9.1.41-0 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/6064918 Email or phone of affected tester (no customers): Slottwo1 sivappa2@gmail.com Issue reported by: Applause Internal Team Device used: Redminote note 10s android 13 App Component: Money Requests
Action Performed:
Launch app
Login with expensifail account
Tap fab and create a new workspace
Tap fab - create expense
Enter amount and tap next
Note report field shows expense report 2025-05-07
Tap create expense entering merchant
Open the expense
Note header and report section
Expected Result:
Both in confirmation page and after creating expense report field must show same details.
Actual Result:
Expense confirmation page shows report as expense report 2025-05-07 but on opening created expense it disappears in a brief time and header & report displays as expense report #7533444478.
@jponikarchuk Can you confirm if this behaviour is reproducible with a normal account? Expensifail is an internal testing account so if it can't be reproduced on a standard account, we can probably close this.
Also the tester email is sivappa2@gmail.com - what Expensifail account were they using?
changed the title [-]Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/-][+][$250] Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/+]on May 9, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dukenv0307@jliexpensify@dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[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. Yes
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon May 7, 2025
Triggered auto assignment to @kadiealexander (
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.kadiealexander commentedon May 8, 2025
Android <> iOS bug swap
jliexpensify commentedon May 8, 2025
@jponikarchuk Can you confirm if this behaviour is reproducible with a normal account? Expensifail is an internal testing account so if it can't be reproduced on a standard account, we can probably close this.
Also the tester email is sivappa2@gmail.com - what Expensifail account were they using?
jponikarchuk commentedon May 8, 2025
@jliexpensify Report field is not available for Gmail user in expense. We can test this with Expensify account only.
[-]Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/-][+][$250] Expense - In report field, Expense report 2025-05-07 is shown briefly & changed to report id[/+]melvin-bot commentedon May 9, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021920643087475662947
36 remaining items
melvin-bot commentedon May 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 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 2025-06-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 26, 2025
@dukenv0307 @jliexpensify @dukenv0307 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
dukenv0307 commentedon May 27, 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: https://github.com/Expensify/App/pull/47468/files#r2108110847
[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. Yes
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
jliexpensify commentedon Jun 3, 2025
Sorting out payment today
jliexpensify commentedon Jun 6, 2025
UGH I am sorry! I totally missed this the other day. Sorting it out now for real!
jliexpensify commentedon Jun 6, 2025
Payment Summary
jliexpensify commentedon Jun 6, 2025
Paid and job closed
quinthar commentedon Sep 17, 2025
$250 approved to @dukenv0307