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-11-20] [$250] Expense-"Hidden" appears in Members list when the workspace is created via Pay with Expensify #51524
Version Number: 9.0.54-1 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail:https://expensify.testrail.io/index.php?/tests/view/5134693 Email or phone of affected tester (no customers):applausetester+kh1610015@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Default individual policy currency for both users must be USD.
Go to staging.new.expensify.com
[User A] Submit an expense in USD to User B
[User B] Go to DM with user A
4/ [User B] Click Pay with Expensify
[User B] Click Business bank account
[User B] Close the RHP
[User B] Go to workspace settings of the newly created workspace
[User B] Go to Members
Expected Result:
There will be no "Hidden" member
Actual Result:
"Hidden" member appears in Members list when the workspace is created via Pay with Expensify in p2p expense
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6645865_1729878847118.20241026_014655.mp4
@zanyrenney 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
[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: Not a critical bug, we don't need to create a discussion.
[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.
Regression Test Proposal
User B requests money to User A in USD
User A press Pay with Expensify and choose Business Bank Account. Note down the new workspace created
Go to the workspace member page of the newly created workspace
Activity
melvin-bot commentedon Oct 26, 2024
Triggered auto assignment to @zanyrenney (
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.lanitochka17 commentedon Oct 26, 2024
@zanyrenney 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
lanitochka17 commentedon Oct 26, 2024
We think that this bug might be related to #wave-collect - Release 1
bernhardoj commentedon Oct 27, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
Hidden is shown in the workspace member after moving the expense to a new workspace.
What is the root cause of that problem?
When we select Business bank account as the payment method, we will optimistically create a new workspace based on the IOU report data.
App/src/components/KYCWall/BaseKYCWall.tsx
Lines 110 to 111 in 652d2ff
The problem is, we are trying to create the workspace member from the IOU report
ownerEmail.App/src/libs/actions/Policy/Policy.ts
Line 2134 in 652d2ff
App/src/libs/actions/Policy/Policy.ts
Lines 2184 to 2191 in 652d2ff
However,
ownerEmaildoesn't exist anymore in the IOU report, onlyownerAccountID, so it defaults to an empty string.What changes do you think we should make in order to solve the problem?
There was previously a plan to get the employee email from the personal detail, but I decided to just default it to an empty string because, at that time, the email wasn't really needed.
Previously, the policy member is keyed by their accountID.

So, the solution is to get the employee's email from the personal details data.
I don't think the personal detail login would be undefined, but we can avoid creating the employee optimistic data if
employeeEmailis empty.zanyrenney commentedon Oct 29, 2024
Wave collect is closed, but adding this to expense.
melvin-bot commentedon Nov 1, 2024
@zanyrenney Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
zanyrenney commentedon Nov 4, 2024
Oops, i thought I added the external label here - my bad!
36 remaining items
hungvu193 commentedon Nov 20, 2024
BugZero Checklist:
Bug classification
Source of bug:
ownerEmailfrom IOU report. However we forgot to update it while selecting Business Bank AccountWhere 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/39489/files#r1849609429
[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: Not a critical bug, we don't need to create a discussion.
[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.
Regression Test Proposal
Do we 👍 or 👎 ?
melvin-bot commentedon Nov 20, 2024
Payment Summary
Upwork Job
BugZero Checklist (@zanyrenney)
bernhardoj commentedon Nov 20, 2024
Requested in ND.
garrettmknight commentedon Nov 20, 2024
@zanyrenney can you confirm the payment summary when you get a chance?
zanyrenney commentedon Nov 21, 2024
sure thing @garrettmknight - sorry about the delay everyone. I was out yesterday.
zanyrenney commentedon Nov 21, 2024
Regression test looks good - getting that added now.
zanyrenney commentedon Nov 21, 2024
https://github.com/Expensify/Expensify/issues/446583
zanyrenney commentedon Nov 21, 2024
Closed job on upwork.
Payment Summary
Reviewer: @hungvu193 owed $250 via NewDot - please request via ND
Reviewer: @bernhardoj owed $250 via NewDot - please request via ND
JmillsExpensify commentedon Nov 21, 2024
$250 approved for @bernhardoj
garrettmknight commentedon Nov 26, 2024
$250 approved for @hungvu193