[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list #40800

lanitochka17 · 2024-04-23T14:00:48Z

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: 1.4.64-0
Reproducible in staging?: Y
Reproducible in production?: Y
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:

Go to Account settings > Workspaces > any workspace
Go to Members
Invite +252 3 234211 which will cause an error
Return to workspace list
Click on the X button to dismiss the error

Expected Result:

The error is dimissed

Actual Result:

The error is not dismissed when clicking on X button in the workspace list

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Add any screenshot/video evidence

Bug6458809_1713877820690.20240423_210639.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0186e1563827cf6717
Upwork Job ID: 1782782840343851008
Last Price Increase: 2024-04-23
Automatic offers:

akinwale | Contributor | 0
bernhardoj | Contributor | 0

Issue Owner

Current Issue Owner: @joekaufmanexpensify

melvin-bot · 2024-04-23T14:00:59Z

Triggered auto assignment to @joekaufmanexpensify (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 · 2024-04-23T14:01:16Z

@joekaufmanexpensify 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 · 2024-04-23T14:01:33Z

We think that this bug might be related to #vip-vsp

dragnoir · 2024-04-23T14:41:52Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

Invite error is not dismissed via X button in the workspace list

What is the root cause of that problem?

This is not a simple issue:

1- the error message is turned from backend as part of policy.errors
It's in english and can't be translated to spanish

2- The area here

displayes all policy.errors and the close button will delete the workspace

App/src/pages/workspace/WorkspaceInitialPage.tsx

Lines 74 to 77 in d296ef8

    
           function dismissError(policyID: string) { 
        
               PolicyUtils.goBackFromInvalidPolicy(); 
        
               Policy.removeWorkspace(policyID); 
        
           }

What changes do you think we should make in order to solve the problem?

1- The backend should turn an error code/string so we can translate

2- The error should be displayed below the members list and not on the left with the menu items

3- Closing the error should only dismiss the message and not remove the workspace

onClose={() => clearMembersErrors();

melvin-bot · 2024-04-23T14:45:28Z

Job added to Upwork: https://www.upwork.com/jobs/~0186e1563827cf6717

joekaufmanexpensify · 2024-04-23T14:45:33Z

this def seems like a bug.

melvin-bot · 2024-04-23T14:45:34Z

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

ZhenjaHorbach · 2024-04-23T15:00:24Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

Workspace - Invite error is not dismissed via X button in the workspace list

What is the root cause of that problem?

The main problem with issue is that for disable error from Workspace list we use pendingAction from policy
But in case of adding an incorrect user, we store this pendingAction inside the list for each user

As result when we try to close error from WorkspacesListPage nothing happened

App/src/pages/workspace/WorkspacesListPage.tsx

Lines 339 to 344 in d296ef8

    
           dismissError: () => { 
        
               if (!policy.pendingAction) { 
        
                   return; 
        
               } 
        
               dismissWorkspaceError(policy.id, policy.pendingAction); 
        
           },

And since we receive an error due to an incorrect user, we need to update the error closure inside the workspace and in the list to just close this error without removing workspace

What changes do you think we should make in order to solve the problem?

I made implementation only for WorkspacesListPage
But we cane make similar and for WorkspaceInitialPage

We can update dismissError like

                    dismissError: () => {
                        const employeeWithError = Object.keys(policy.employeeList)?.find(
                            (employee) => policy.employeeList[employee]?.errors && !isEmptyObject(policy.employeeList[employee]?.errors),
                        );
                        if (!policy.pendingAction && !employeeWithError) {
                            return;
                        }
                        dismissWorkspaceError(policy.id, policy.pendingAction, policy.employeeList?.[employeeWithError]?.pendingAction);
                    },

App/src/pages/workspace/WorkspacesListPage.tsx

Lines 339 to 344 in d296ef8

    
           dismissError: () => { 
        
               if (!policy.pendingAction) { 
        
                   return; 
        
               } 
        
               dismissWorkspaceError(policy.id, policy.pendingAction); 
        
           },

And then update dismissWorkspaceError

function dismissWorkspaceError(policyID: string, pendingAction: OnyxCommon.PendingAction, employeePendingAction: OnyxCommon.PendingAction) {
    if (pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE) {
        Policy.clearDeleteWorkspaceError(policyID);
        return;
    }

    if (pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD) {
        Policy.removeWorkspace(policyID);
        return;
    }

    if (employeePendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD) {
        Policy.clearErrors(policyID);
        return;
    }
    throw new Error('Not implemented');
}

Plus we need update setWorkspaceErrors for removing current errors and error from employee list

App/src/libs/actions/Policy.ts

Lines 1789 to 1796 in d296ef8

    
           function setWorkspaceErrors(policyID: string, errors: Errors) { 
        
               if (!allPolicies?.[policyID]) { 
        
                   return; 
        
               } 
        
               Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors: null}); 
        
               Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors}); 
        
           }

Similar implementation we can make and for error inside workspace initial page

App/src/pages/workspace/WorkspaceInitialPage.tsx

Lines 74 to 77 in d296ef8

    
           function dismissError(policyID: string) { 
        
               PolicyUtils.goBackFromInvalidPolicy(); 
        
               Policy.removeWorkspace(policyID); 
        
           }

What alternative solutions did you explore? (Optional)

NA

bernhardoj · 2024-04-23T15:11:18Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

There are 3 issues here, first, the failed member and its error message don't show like before. Second, when we close the invite error message, the policy is removed and we are navigated back to the workspace list. Last, we can't clear the error from workspace list page/

What is the root cause of that problem?

For the first problem, we get the member data from getMemberAccountIDsForWorkspace

App/src/pages/workspace/WorkspaceMembersPage.tsx

Line 75 in d296ef8

    
           const policyMemberEmailsToAccountIDs = useMemo(() => PolicyUtils.getMemberAccountIDsForWorkspace(policy?.employeeList), [policy?.employeeList]);

However, getMemberAccountIDsForWorkspace ignores member that has an error.

App/src/libs/PolicyUtils.ts

Lines 157 to 159 in d296ef8

    
           if (Object.keys(member?.errors ?? {})?.length > 0) { 
        
               return; 
        
           }

For the second problem, when closing the error message, we call dismissError which will navigate the user back to the workspace list page and remove the workspace.

App/src/pages/workspace/WorkspaceInitialPage.tsx

Lines 74 to 77 in d296ef8

    
           function dismissError(policyID: string) { 
        
               PolicyUtils.goBackFromInvalidPolicy(); 
        
               Policy.removeWorkspace(policyID); 
        
           }

For the 3rd problem, if there is no pending action, which is true for our case, we just do nothing.

App/src/pages/workspace/WorkspacesListPage.tsx

Lines 339 to 344 in 7924597

    
           dismissError: () => { 
        
               if (!policy.pendingAction) { 
        
                   return; 
        
               } 
        
               dismissWorkspaceError(policy.id, policy.pendingAction); 
        
           },

What changes do you think we should make in order to solve the problem?

For the first problem, we can add a new param to getMemberAccountIDsForWorkspace to include members with errors. This will show the member that has an error, however, the member won't show optimistically when we add it and only shows when there is an error. This is because we assign the optimistic member with a login from invitedEmailsToAccountIDs and the login from invitedEmailsToAccountIDs for phone number doesn't have @expensify.sms suffix, so when we search for the personal detail, we won't find anything and the member won't show.

App/src/libs/actions/Policy.ts

Lines 1403 to 1409 in b8d1908

    
           Object.keys(invitedEmailsToAccountIDs).forEach((email) => { 
        
               optimisticMembersState[email] = {pendingAction: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD, role: CONST.POLICY.ROLE.USER}; 
        
               successMembersState[email] = {pendingAction: null}; 
        
               failureMembersState[email] = { 
        
                   errors: ErrorUtils.getMicroSecondOnyxError('workspace.people.error.genericAdd'), 
        
               }; 
        
           });

To fix it, we should iterate over logins instead.

App/src/libs/actions/Policy.ts

Line 1389 in b8d1908

    
           const logins = Object.keys(invitedEmailsToAccountIDs).map((memberLogin) => PhoneNumber.addSMSDomainIfPhoneNumber(memberLogin));

logins.forEach((email) => { ...

we also need to add personalDetails to this memo deps, otherwise it won't recalculate when personalDetails is updated.

App/src/pages/workspace/WorkspaceMembersPage.tsx

Line 75 in b8d1908

    
           const policyMemberEmailsToAccountIDs = useMemo(() => PolicyUtils.getMemberAccountIDsForWorkspace(policy?.employeeList), [policy?.employeeList]);

In 3rd problem, we already handle the case for add/delete pending action.

App/src/pages/workspace/WorkspacesListPage.tsx

Lines 105 to 116 in 7924597

    
           function dismissWorkspaceError(policyID: string, pendingAction: OnyxCommon.PendingAction) { 
        
               if (pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.DELETE) { 
        
                   Policy.clearDeleteWorkspaceError(policyID); 
        
                   return; 
        
               } 
        
               if (pendingAction === CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD) { 
        
                   Policy.removeWorkspace(policyID); 
        
                   return; 
        
               } 
        
               throw new Error('Not implemented'); 
        
           }

To solve the 3rd problem, we will remove the pending action check from the code below.

App/src/pages/workspace/WorkspacesListPage.tsx

Lines 340 to 343 in 7924597

    
           if (!policy.pendingAction) { 
        
               return; 
        
           } 
        
           dismissWorkspaceError(policy.id, policy.pendingAction);

In dismissWorkspaceError, if the pending action is empty, then we just want to clear the error. We have Policy.clearErrors,

App/src/libs/actions/Policy.ts

Lines 2503 to 2506 in a852ea7

    
           function clearErrors(policyID: string) { 
        
               setWorkspaceErrors(policyID, {}); 
        
               hideWorkspaceAlertMessage(policyID); 
        
           }

but it doesn't work because we accessed the key wrongly, it should be

if (!allPolicies?.[`${ONYXKEYS.COLLECTION.POLICY}${policyID}`])

but even if we fix this one, looks like the double merge with a null and empty object doesn't work at all.

App/src/libs/actions/Policy.ts

Lines 1789 to 1796 in a852ea7

    
           function setWorkspaceErrors(policyID: string, errors: Errors) { 
        
               if (!allPolicies?.[policyID]) { 
        
                   return; 
        
               } 
        
               Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors: null}); 
        
               Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors}); 
        
           }

To simplify it, we can just update Policy.clearErrors to replace setWorkspaceErrors with

Onyx.merge(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {errors: null});

To solve the 2nd problem, we will update the onClose code of the error to be like this. We check !policyID for invalid policy ID error. I don't think we need to add for delete case like in above, but if we want to add it, we can just add it to follow the similar pattern in dismissWorkspaceError above.

onClose={() => {
    if (!policyID || policy?.pendingAction == 'add') {
        dismissError(policyID)
    } else {
        Policy.clearErrors(policyID);
    }
}}

bernhardoj · 2024-04-23T15:47:57Z

Updated proposal to include more fix

joekaufmanexpensify · 2024-04-24T13:33:38Z

Proposals pending review

joekaufmanexpensify · 2024-04-25T13:51:06Z

@Santhosh-Sellavel mind reviewing?

Santhosh-Sellavel · 2024-04-25T14:05:12Z

Sorry this one, skipped my list will get to it later today!

joekaufmanexpensify · 2024-04-26T13:58:51Z

TY!

joekaufmanexpensify · 2024-04-29T14:14:05Z

Pending review from @Santhosh-Sellavel

Santhosh-Sellavel · 2024-04-29T19:01:36Z

Sorry for the back and forth. I'm Just gonna unassign this as my bandwidth is too low. Asked here for volunteers

Santhosh-Sellavel · 2024-04-29T19:02:05Z

@arosiclair Will takeover this as C+!

akinwale · 2024-04-30T06:14:44Z

Looks like an auto complete error above. Taking over here as C+.

melvin-bot · 2024-05-01T09:51:21Z

📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

bernhardoj · 2024-05-02T04:15:42Z

PR is ready

cc: @akinwale

melvin-bot · 2024-05-13T08:11:10Z

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot · 2024-05-13T08:11:15Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.72-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Fix can't dismiss workspace member invite error #41478

If no regressions arise, payment will be issued on 2024-05-20. 🎊

For reference, here are some details about the assignees on this issue:

@akinwale requires payment automatic offer (Contributor)
@bernhardoj requires payment automatic offer (Contributor)

melvin-bot · 2024-05-13T08:11:16Z

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:

[@akinwale] The PR that introduced the bug has been identified. Link to the PR: N/A
[@akinwale] 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
[@akinwale] 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: N/A
[@akinwale] Determine if we should create a regression test for this bug.
[@akinwale] 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.
[@joekaufmanexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon: N/A

joekaufmanexpensify · 2024-05-13T14:16:49Z

@akinwale could you please handle the BZ checklist this week so we can prep for payment?

joekaufmanexpensify · 2024-05-20T13:55:18Z

bump @akinwale could you please handle BZ here so we can issue payment?

akinwale · 2024-05-20T14:02:03Z

[@akinwale] The PR that introduced the bug has been identified. Link to the PR:

[@akinwale] 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:

[@akinwale] 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:

Not a regression. This was not being specifically handled.

[@akinwale] Determine if we should create a regression test for this bug.

[@akinwale] 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.

Regression Test Steps

Launch Expensify.
Open the workspace members as a workspace admin.
Invite +252 3 234211.
Verify that the invited member is displayed with an error message.
Clear the displayed error message.
On the workspace settings page, clear the error message.
Verify that the error message is cleared.
Repeat steps 2 through 4.
Navigate back to the workspace list page.
Clear the error message displayed below the list of workspace items.
Verify that the error message is cleared.

Do we agree 👍 or 👎?

akinwale · 2024-05-20T14:02:11Z

@joekaufmanexpensify Done!

joekaufmanexpensify · 2024-05-20T15:30:57Z

Hmm, I feel like this is a pretty niche issue. I feel like it's fine to have no regression test for this.

joekaufmanexpensify · 2024-05-20T15:31:03Z

Checklist is complete!

joekaufmanexpensify · 2024-05-20T15:31:49Z

All set to issue payment. We need to pay:

@bernhardoj - $250 for PR via upwork.
@akinwale - $250 for C+ via upwork.

joekaufmanexpensify · 2024-05-20T15:33:50Z

@bernhardoj $250 sent and contract ended!

joekaufmanexpensify · 2024-05-20T15:33:58Z

@akinwale $250 sent and contract ended!

joekaufmanexpensify · 2024-05-20T15:34:03Z

Upwork job closed.

joekaufmanexpensify · 2024-05-20T15:34:10Z

All set, TY everyone!

lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Apr 23, 2024

melvin-bot bot assigned joekaufmanexpensify Apr 23, 2024

joekaufmanexpensify added the External Added to denote the issue can be worked on by a contributor label Apr 23, 2024

melvin-bot bot changed the title ~~Workspace - Invite error is not dismissed via X button in the workspace list~~ [$250] Workspace - Invite error is not dismissed via X button in the workspace list Apr 23, 2024

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Apr 23, 2024

melvin-bot bot assigned Santhosh-Sellavel Apr 23, 2024

joekaufmanexpensify added this to [#whatsnext] #wave-collect Apr 23, 2024

ZhenjaHorbach mentioned this issue Apr 25, 2024

Android - Workspace-Closing the error message "unable to add members to WS", deletes the WS #41037

Closed

6 tasks

melvin-bot bot added the Overdue label Apr 29, 2024

melvin-bot bot removed the Overdue label Apr 29, 2024

arosiclair assigned akinwale Apr 30, 2024

bernhardoj mentioned this issue May 2, 2024

Fix can't dismiss workspace member invite error #41478

Merged

50 tasks

melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels May 2, 2024

trjExpensify moved this to Polish in [#whatsnext] #wave-collect May 2, 2024

melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels May 13, 2024

melvin-bot bot changed the title ~~[$250] Workspace - Invite error is not dismissed via X button in the workspace list~~ [HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list May 13, 2024

melvin-bot bot removed the Reviewing Has a PR in review label May 13, 2024

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels May 19, 2024

joekaufmanexpensify closed this as completed May 20, 2024

github-project-automation bot moved this from Polish to Done in [#whatsnext] #wave-collect May 20, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list #40800

[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list #40800

lanitochka17 commented Apr 23, 2024 •

edited by melvin-bot bot

Loading

melvin-bot bot commented Apr 23, 2024

lanitochka17 commented Apr 23, 2024

lanitochka17 commented Apr 23, 2024

dragnoir commented Apr 23, 2024

melvin-bot bot commented Apr 23, 2024

joekaufmanexpensify commented Apr 23, 2024

melvin-bot bot commented Apr 23, 2024

ZhenjaHorbach commented Apr 23, 2024 •

edited

Loading

bernhardoj commented Apr 23, 2024 •

edited

Loading

bernhardoj commented Apr 23, 2024

joekaufmanexpensify commented Apr 24, 2024

joekaufmanexpensify commented Apr 25, 2024

Santhosh-Sellavel commented Apr 25, 2024

joekaufmanexpensify commented Apr 26, 2024

joekaufmanexpensify commented Apr 29, 2024

Santhosh-Sellavel commented Apr 29, 2024

Santhosh-Sellavel commented Apr 29, 2024

akinwale commented Apr 30, 2024

melvin-bot bot commented May 1, 2024

bernhardoj commented May 2, 2024

melvin-bot bot commented May 13, 2024

melvin-bot bot commented May 13, 2024

melvin-bot bot commented May 13, 2024 •

edited by joekaufmanexpensify

Loading

joekaufmanexpensify commented May 13, 2024

joekaufmanexpensify commented May 20, 2024

akinwale commented May 20, 2024

akinwale commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list #40800

[HOLD for payment 2024-05-20] [$250] Workspace - Invite error is not dismissed via X button in the workspace list #40800

Comments

lanitochka17 commented Apr 23, 2024 • edited by melvin-bot bot Loading

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

melvin-bot bot commented Apr 23, 2024

lanitochka17 commented Apr 23, 2024

lanitochka17 commented Apr 23, 2024

dragnoir commented Apr 23, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

melvin-bot bot commented Apr 23, 2024

joekaufmanexpensify commented Apr 23, 2024

melvin-bot bot commented Apr 23, 2024

ZhenjaHorbach commented Apr 23, 2024 • edited Loading

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What alternative solutions did you explore? (Optional)

bernhardoj commented Apr 23, 2024 • edited Loading

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

bernhardoj commented Apr 23, 2024

joekaufmanexpensify commented Apr 24, 2024

joekaufmanexpensify commented Apr 25, 2024

Santhosh-Sellavel commented Apr 25, 2024

joekaufmanexpensify commented Apr 26, 2024

joekaufmanexpensify commented Apr 29, 2024

Santhosh-Sellavel commented Apr 29, 2024

Santhosh-Sellavel commented Apr 29, 2024

akinwale commented Apr 30, 2024

melvin-bot bot commented May 1, 2024

bernhardoj commented May 2, 2024

melvin-bot bot commented May 13, 2024

melvin-bot bot commented May 13, 2024

melvin-bot bot commented May 13, 2024 • edited by joekaufmanexpensify Loading

joekaufmanexpensify commented May 13, 2024

joekaufmanexpensify commented May 20, 2024

akinwale commented May 20, 2024

akinwale commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

joekaufmanexpensify commented May 20, 2024

lanitochka17 commented Apr 23, 2024 •

edited by melvin-bot bot

Loading

ZhenjaHorbach commented Apr 23, 2024 •

edited

Loading

bernhardoj commented Apr 23, 2024 •

edited

Loading

melvin-bot bot commented May 13, 2024 •

edited by joekaufmanexpensify

Loading