[HOLD for payment 2023-10-21] [$500] Focus freeze on add contact method magic code on coming back from search #28340

lanitochka17 · 2023-09-27T18:14:26Z

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Action Performed:

Open the app
Open settings->profile->contact method
Open pending contact method or add new contact method and open the contact method
Observe that currently on all digits, I cursor is visible and we can change focus to other digits
Focus back to first digit and press CTRL+K/CMD+K to open search
Click on back and now observe that normal cursor is displayed over digits and we cannot click and change focus

Expected Result:

Focus should not freeze when we come back to add contact method magic code page from search

Actual Result:

Focus freezes when we come back to add contact method magic code page from search

Workaround:

Unknown

Platforms:

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

Version Number: 1.3.74-2

Reproducible in staging?: Yes

Reproducible in production?: Yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

mac.chrome.desktop.focus.freeze.on.back.from.search.magic.code.mov

Recording.98.mp4

Expensify/Expensify Issue URL:

Issue reported by: @dhanashree-sawant

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695744610116319

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ba4effd8bd80f395
Upwork Job ID: 1707096387145940992
Last Price Increase: 2023-09-27
Automatic offers:

mollfpr | Reviewer | 26975575
tienifr | Contributor | 26975578
dhanashree-sawant | Reporter | 26975582

melvin-bot · 2023-09-27T18:14:31Z

Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

melvin-bot · 2023-09-27T18:14:31Z

Job added to Upwork: https://www.upwork.com/jobs/~01ba4effd8bd80f395

melvin-bot · 2023-09-27T18:14:33Z

Bug0 Triage Checklist (Main S/O)

This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
This bug is not a duplicate report (check E/App issues and #expensify-bugs)
- If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
This bug is reproducible using the reproduction steps in the OP. S/O
- If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
- If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
This issue is filled out as thoroughly and clearly as possible
- Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

melvin-bot · 2023-09-27T18:14:37Z

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

redpanda-bit · 2023-09-27T21:21:30Z

Proposal

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

Input loses the ability to focus after going to search and coming back to input.

What is the root cause of that problem?

The behavior of the MagicCodeInput relies on the method onEntryTransitionEnd to be called in order to function as expected. However, navigating to search while the input is visible blurs the input, and going back to the MagicCodeInput does not cause the onEntryTransitionEnd method to be called, and therefore, the expected behavior goes away when we navigate to search from the MagicCodeInput since the focus is lost and not recovered.

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

We can add a new event listener to ScreenWrapper to listen for onFocus instead of onEntryTransitionEnd. OnFocus gets called every time the screens goes from not visible->visible regardless of the screen already being present in the navigation history or not. This would allow to call focus on the input whenever the input goes into view. This would have the MagicCodeInput restored to its expected behavior.

Make use of the new onFocus prop instead of onEntryTransitionEnd.

App/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js

Lines 234 to 238 in 7d32e61

    
           return ( 
        
               <ScreenWrapper 
        
                   onEntryTransitionEnd={() => this.validateCodeFormRef.current && this.validateCodeFormRef.current.focus()} 
        
                   testID={ContactMethodDetailsPage.displayName} 
        
               >

And add the code below along with unsubscribe to https://github.com/Expensify/App/blob/main/src/components/ScreenWrapper/index.js:

        if (this.props.onFocus) {
            this.unsubscribeOnFocus = this.props.navigation.addListener('focus', () => {
                this.props.onFocus();
            });
        }

What alternative solutions did you explore? (Optional)

Adding onFocusEffect to https://github.com/Expensify/App/blob/main/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js and manually focus on the input. Additionally, remove the onEntryTransitionEnd from the ScreenWrapper component.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Krishna2323 · 2023-09-27T22:24:46Z

Proposal

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

Focus freeze on add contact method magic code on coming back from search .

What is the root cause of that problem?

When the MagicCodeInput is active and you navigate to the search, the input loses focus. Upon returning, the onEntryTransitionEnd method isn't triggered. This disrupts the expected behavior since the focus on the input isn't automatically restored.
There is also a height glitch that sets the input height to '0px' even if the height style is set to '52px'.

Height Glitch:

height_glitch.mp4

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

We should add a useFocusEffect hook inside BaseValidateCodeForm to focus on the input whenever the screen is focused.

    useFocusEffect(
        useCallback(() => {
            if (!inputValidateCodeRef.current) {
                return;
            }
            inputValidateCodeRef.current.focus();
        }, []),
    );

For the height glitch we can pass a prop to BaseTextInput called transparent and we will only set the height if the tranaparent is a falsy value or we can directly set the height to 100% or auto on the input.

!isMultiline && !props.transparent && {height, lineHeight},

Result:

fix_demo.mp4

tienifr · 2023-09-28T09:43:12Z

Proposal

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

In

App/src/components/TextInput/BaseTextInput.js

Lines 140 to 143 in 67d4a7a

    
           const layout = event.nativeEvent.layout; 
        
           setWidth((prevWidth) => (props.autoGrowHeight ? layout.width : prevWidth)); 
        
           setHeight((prevHeight) => (!props.multiline ? layout.height : prevHeight));

we're calculating the height of the input based on onLayout function, but when we navigate to the new page, the layout.height will return 0. Ref: facebook/react-native#10743

After come back to 2FA page, the layout.height is 52px, but we're using transitionDelay:99999s for 2FA input here, that makes the input height is still 0

-> we can't interactive with the input

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

Here is the PR that add transitionDelay: 99999s, and I'm sure that we just need transitionDelay for background-color so we shouldn't apply transitionDelay for all transition

-> we need to add transitionProperty: 'background-color' to inputTransparent

After back to 2FA page, we need to focus on the input as well, in order to achieve that we can call inputValidateCodeRef.current.focus(); in useFocusEffect hook

    useFocusEffect(
        useCallback(() => {
            if (!inputValidateCodeRef.current) {
                return;
            }
            setTimeout(() => inputValidateCodeRef.current.focus(), CONST.ANIMATED_TRANSITION);
        }, []),
    );

we need to use setTimeout here to wait for navigation end. We already discuss this problem in this conversation

Or we can use useAutoFocusInput after this solution is merged

What alternative solutions did you explore? (Optional)

in onLayout function we can apply the condition to prevent updating the height to 0

mollfpr · 2023-09-28T11:41:15Z

@redpanda-bit Your main solution is not working. So the issue is not about the input not just focusing after the back from the search page.

For the height glitch we can pass a prop to BaseTextInput called transparent and we will only set the height if the tranaparent is a falsy value or we can directly set the height to 100% or auto on the input.

@Krishna2323 I don't understand this solution. What is defining the value of transparent? Does the auto focus is work without setTimeout?

@tienifr We can use the same pattern https://expensify.slack.com/archives/C01GTK53T8Q/p1694660990479979 for auto focus an input.

Could you confirm it's working before #21482? Removing the transitionDelay does fixing the issue, so I think you got the RCA correct.

tienifr · 2023-09-28T12:31:19Z

@mollfpr yes it worked before, but we can not revert this PR. What do you think about my proposal above? Thanks

mollfpr · 2023-09-28T14:13:18Z

@tienifr It's looks good. Looking at the offending PR, they aim to delay the background-color transition in the first place.

Could you check if the issue of #21482 is still fixed?

tienifr · 2023-09-29T02:45:30Z

@mollfpr It still works after applying transitionProperty

Screen.Recording.2023-09-29.at.09.43.39.mov

mollfpr · 2023-09-29T12:50:46Z

Thanks @tienifr

The proposal from @tienifr looks good to me!

For the autofocus input, we can follow the recommendation https://expensify.slack.com/archives/C01GTK53T8Q/p1694660990479979

🎀 👀 🎀 C+ reviewed!

melvin-bot · 2023-09-29T12:50:52Z

Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

melvin-bot · 2023-10-02T08:25:53Z

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

Offer link
Upwork job

melvin-bot · 2023-10-02T08:25:57Z

📣 @tienifr 🎉 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 📖

melvin-bot · 2023-10-02T08:26:01Z

📣 @dhanashree-sawant 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

grgia · 2023-10-02T08:26:12Z

Assigned @tienifr!

melvin-bot · 2023-10-13T22:01:30Z

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

fix: 28340 Focus freeze on add contact method magic code on coming back from search #28682

If no regressions arise, payment will be issued on 2023-10-20. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

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

@mollfpr requires payment offer (Reviewer)
@tienifr requires payment offer (Contributor)
@dhanashree-sawant requires payment offer (Reporter)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

melvin-bot · 2023-10-13T22:01:31Z

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:

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

melvin-bot · 2023-10-13T22:53:39Z

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

fix: 28340 Focus freeze on add contact method magic code on coming back from search #28682

If no regressions arise, payment will be issued on 2023-10-20. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

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

@mollfpr requires payment offer (Reviewer)
@tienifr requires payment offer (Contributor)
@dhanashree-sawant requires payment offer (Reporter)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

melvin-bot · 2023-10-13T22:53:41Z

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:

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

melvin-bot · 2023-10-16T21:16:15Z

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

fix: 28340 Focus freeze on add contact method magic code on coming back from search #28682

If no regressions arise, payment will be issued on 2023-10-23. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

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

@mollfpr requires payment offer (Reviewer)
@tienifr requires payment offer (Contributor)
@dhanashree-sawant requires payment offer (Reporter)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

melvin-bot · 2023-10-16T21:16:17Z

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:

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

melvin-bot · 2023-10-16T21:41:52Z

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

fix: 28340 Focus freeze on add contact method magic code on coming back from search #28682

If no regressions arise, payment will be issued on 2023-10-23. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR

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

@mollfpr requires payment offer (Reviewer)
@tienifr requires payment offer (Contributor)
@dhanashree-sawant requires payment offer (Reporter)

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

melvin-bot · 2023-10-16T21:41:54Z

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:

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

mollfpr · 2023-10-20T16:54:06Z

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

#21482

[@mollfpr] 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/21482/files#r1367256050

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

I don't think we can prevent this kind of bug with the checklist since it's very specific things to check. So the regression step should be enough.

[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] 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.

Open the app
Open settings->profile->contact method
Open pending contact method or add new contact method and open the contact method
Observe that currently on all digits, I cursor is visible and we can change focus to other digits
Focus back to first digit and press CTRL+K/CMD+K to open search
Click on back
Verify that the input is focus and we can use it without being freeze

@jliexpensify Could you confirm which date payment is the correct one?

jliexpensify · 2023-10-22T03:03:42Z

This is the PR right?

if so, it was deployed to prod on October 14th, so payment date should be 21st. But I do see there were 2 failures - this doesn't matter right?:

jliexpensify · 2023-10-22T03:06:23Z

Payment Summary:

Bug Reporter: @dhanashree-sawant $50
Contributor: @tienifr $500
C+: @mollfpr $500 - New.Dot

Upwork job

mollfpr · 2023-10-22T08:27:15Z

if so, it was deployed to prod on October 14th, so payment date should be 21st. But I do see there were 2 failures - this doesn't matter right?:

Probably, yes!

@jliexpensify I'll request the payment in NewDot, thank you!

jliexpensify · 2023-10-22T09:51:58Z

Oh didn't realise you qualify for ND payments. Have adjusted above and will cancel your offer @mollfpr

jliexpensify · 2023-10-22T09:55:15Z

Paid and job closed!

JmillsExpensify · 2023-10-23T16:45:45Z

$500 payment approved for @mollfpr based on summary above.

lanitochka17 added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Sep 27, 2023

melvin-bot bot assigned jliexpensify Sep 27, 2023

melvin-bot bot changed the title ~~Focus freeze on add contact method magic code on coming back from search~~ [$500] Focus freeze on add contact method magic code on coming back from search Sep 27, 2023

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 27, 2023

melvin-bot bot assigned mollfpr Sep 27, 2023

melvin-bot bot assigned grgia Sep 29, 2023

melvin-bot bot added the Overdue label Oct 2, 2023

grgia assigned tienifr Oct 2, 2023

melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 2, 2023

melvin-bot bot removed the Overdue label Oct 2, 2023

tienifr mentioned this issue Oct 3, 2023

fix: 28340 Focus freeze on add contact method magic code on coming back from search #28682

Merged

59 tasks

melvin-bot bot removed the Reviewing Has a PR in review label Oct 13, 2023

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Oct 13, 2023

melvin-bot bot changed the title ~~[HOLD for payment 2023-10-20] [$500] Focus freeze on add contact method magic code on coming back from search~~ [HOLD for payment 2023-10-20] [HOLD for payment 2023-10-20] [$500] Focus freeze on add contact method magic code on coming back from search Oct 13, 2023

melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Oct 16, 2023

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Oct 20, 2023

mollfpr mentioned this issue Oct 20, 2023

Fix OTP autofill in iOS Safari #21482

Merged

57 tasks

jliexpensify closed this as completed Oct 22, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HOLD for payment 2023-10-21] [$500] Focus freeze on add contact method magic code on coming back from search #28340

[HOLD for payment 2023-10-21] [$500] Focus freeze on add contact method magic code on coming back from search #28340

lanitochka17 commented Sep 27, 2023 •

edited by melvin-bot bot

Loading

melvin-bot bot commented Sep 27, 2023

melvin-bot bot commented Sep 27, 2023

melvin-bot bot commented Sep 27, 2023

melvin-bot bot commented Sep 27, 2023

redpanda-bit commented Sep 27, 2023

Krishna2323 commented Sep 27, 2023

tienifr commented Sep 28, 2023

mollfpr commented Sep 28, 2023

tienifr commented Sep 28, 2023

mollfpr commented Sep 28, 2023

tienifr commented Sep 29, 2023

mollfpr commented Sep 29, 2023

melvin-bot bot commented Sep 29, 2023

melvin-bot bot commented Oct 2, 2023

melvin-bot bot commented Oct 2, 2023

melvin-bot bot commented Oct 2, 2023

grgia commented Oct 2, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

mollfpr commented Oct 20, 2023

jliexpensify commented Oct 22, 2023

jliexpensify commented Oct 22, 2023 •

edited

Loading

mollfpr commented Oct 22, 2023

jliexpensify commented Oct 22, 2023

jliexpensify commented Oct 22, 2023

JmillsExpensify commented Oct 23, 2023

[HOLD for payment 2023-10-21] [$500] Focus freeze on add contact method magic code on coming back from search #28340

[HOLD for payment 2023-10-21] [$500] Focus freeze on add contact method magic code on coming back from search #28340

Comments

lanitochka17 commented Sep 27, 2023 • edited by melvin-bot bot Loading

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

melvin-bot bot commented Sep 27, 2023

melvin-bot bot commented Sep 27, 2023

melvin-bot bot commented Sep 27, 2023

Bug0 Triage Checklist (Main S/O)

melvin-bot bot commented Sep 27, 2023

redpanda-bit commented Sep 27, 2023

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)

Krishna2323 commented Sep 27, 2023

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?

Result:

tienifr commented Sep 28, 2023

Proposal

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

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

What alternative solutions did you explore? (Optional)

mollfpr commented Sep 28, 2023

tienifr commented Sep 28, 2023

mollfpr commented Sep 28, 2023

tienifr commented Sep 29, 2023

mollfpr commented Sep 29, 2023

melvin-bot bot commented Sep 29, 2023

melvin-bot bot commented Oct 2, 2023

melvin-bot bot commented Oct 2, 2023

melvin-bot bot commented Oct 2, 2023

grgia commented Oct 2, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 13, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

melvin-bot bot commented Oct 16, 2023

mollfpr commented Oct 20, 2023

jliexpensify commented Oct 22, 2023

jliexpensify commented Oct 22, 2023 • edited Loading

mollfpr commented Oct 22, 2023

jliexpensify commented Oct 22, 2023

jliexpensify commented Oct 22, 2023

JmillsExpensify commented Oct 23, 2023

lanitochka17 commented Sep 27, 2023 •

edited by melvin-bot bot

Loading

jliexpensify commented Oct 22, 2023 •

edited

Loading