[W4Checklist] [Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update #60709

m-natarajan · 2025-04-23T10:28:25Z

melvin-bot · 2025-04-23T10:28:38Z

Triggered auto assignment to @strepanier03 (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.

MelvinBot · 2025-04-23T10:29:23Z

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

shubham1206agra · 2025-04-23T10:35:10Z

Screen.Recording.2025-04-23.at.4.04.44.PM.mov

Able to repro this. This happens only once when I open the App.

linhvovan29546 · 2025-04-23T12:19:20Z

🚨 Edited by proposal-police: This proposal was edited at 2025-04-23 12:25:46 UTC.

Proposal

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

Cmd+K Navigation Fails to Open Chat After Desktop Update

What is the root cause of that problem?

In the #56948 We updated SearchAutocompleteList, we have disableKeyboardShortcuts={!shouldSubscribeToArrowKeyEvents}. This disables the Enter shortcut when shouldSubscribeToArrowKeyEvents is either false or undefined. That flag default is undefined. And, in SearchRouter, we render the SearchAutocompleteList without that flag, which leading to the disableKeyboardShortcuts is true, then nothing happen when press enter

App/src/components/Search/SearchAutocompleteList.tsx

Lines 600 to 601 in 8a9ecc6

    
           shouldSubscribeToArrowKeyEvents={shouldSubscribeToArrowKeyEvents} 
        
           disableKeyboardShortcuts={!shouldSubscribeToArrowKeyEvents}

App/src/components/SelectionList/BaseSelectionList.tsx

Lines 822 to 828 in 806e231

    
           useKeyboardShortcut(CONST.KEYBOARD_SHORTCUTS.ENTER, selectFocusedOption, { 
        
               captureOnInputs: true, 
        
               shouldBubble: !flattenedSections.allOptions.at(focusedIndex) || focusedIndex === -1, 
        
               shouldStopPropagation, 
        
               shouldPreventDefault, 
        
               isActive: !disableKeyboardShortcuts && !disableEnterShortcut && isFocused && focusedIndex >= 0, 
        
           });

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

We have two options:

Option 1:
Set shouldSubscribeToArrowKeyEvents = true by default in SearchAutocompleteList, as the issue in that PR seems to an edge case.

App/src/components/Search/SearchAutocompleteList.tsx

Lines 130 to 138 in 8a9ecc6

    
           function SearchAutocompleteList( 
        
               { 
        
                   autocompleteQueryValue, 
        
                   searchQueryItem, 
        
                   getAdditionalSections, 
        
                   onListItemPress, 
        
                   setTextQuery, 
        
                   updateAutocompleteSubstitutions, 
        
                   shouldSubscribeToArrowKeyEvents,

shouldSubscribeToArrowKeyEvents = true

Option 2:
Explicitly pass shouldSubscribeToArrowKeyEvents={true} from SearchRouter.

App/src/components/Search/SearchRouter/SearchRouter.tsx

Lines 348 to 350 in 8a9ecc6

    
           <SearchAutocompleteList 
        
               autocompleteQueryValue={autocompleteQueryValue || textInputValue} 
        
               searchQueryItem={searchQueryItem}

                    <SearchAutocompleteList
                        shouldSubscribeToArrowKeyEvents

We can check other places, like this one, to see if a similar issue exists.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

I think automated tests are not necessary in this case since we're making shouldSubscribeToArrowKeyEvents default to true. If a value of false is passed explicitly, it would be intentional.

What alternative solutions did you explore? (Optional)

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.

ishakakkad · 2025-04-23T15:55:24Z

🚨 Edited by proposal-police: This proposal was edited at 2025-04-23 15:58:56 UTC.

Proposal

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

Item does not select using keyboard navigation, when first time open the search dialog on chat page.

What is the root cause of that problem?

When the search dialog is opened for the first time, the search input loses focus when arrow keys are pressed. As a result, pressing the Enter key does not trigger item selection. However, this issue does not occur when the dialog is opened subsequently—the search input retains focus during arrow key navigation, and Enter works as expected. This issue is occurred because of this condition.

On the first render, areOptionsInitialized is false. It only becomes true after a component re-render triggered by options loading. During this initial phase, pressing arrow keys causes the search input to lose focus, leading to the unexpected behavior.

On subsequent openings of the search dialog, the options have already been initialized, so areOptionsInitialized remains true from the start. This allows arrow key navigation without affecting the input focus, and Enter correctly selects the highlighted item.

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

Solution 1

To fix this issue we need to add areOptionsInitialized check before loading search input as well. We can make following changes here

const {areOptionsInitialized} = useOptionsList();

 {isRecentSearchesDataLoaded && areOptionsInitialized && (
    <>
        <SearchInputSelectionWrapper

Note: Also, we need to check other places where we used SearchAutocompleteList and make the same changes if needed.

Solution 2

We can add following code inside SearchRouter

useLayoutEffect(() => {
if (textInputRef.current && textInputRef.current.isFocused()) {
        setTimeout(() => {
            textInputRef?.current?.blur();
            textInputRef?.current?.focus();
        }, 0);
    }
}, [textInputRef.current]);

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

UI bug so NA

What alternative solutions did you explore? (Optional)

Initialize options when the provider is mounted here (not ideal solution)

useEffect(() => {
        if (!isLoadingApp && !areOptionsInitialized.current && personalDetails && reports) {
            const optionLists = createOptionList(personalDetails, reports);
            setOptions({
                reports: optionLists.reports,
                personalDetails: optionLists.personalDetails,
            });
            areOptionsInitialized.current = true;
        }
    }, [isLoadingApp, personalDetails, reports]);

thelullabyy · 2025-04-23T18:38:16Z

Proposal

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

When a user opens the search route for the first time and types a query, pressing "Enter" does nothing. The expected behavior is that the top search result is selected, but instead, users must manually click with the mouse or trackpad to proceed.

What is the root cause of that problem?

This issue occurs only the first time a user opens the search route. When the search route opens, the search input is automatically focused:

App/src/components/Search/SearchAutocompleteList.tsx

Line 577 in 18f248c

areOptionsInitialized && (

This triggers the onFocus callback in SearchAutocompleteInput.tsx:

App/src/components/Search/SearchAutocompleteInput.tsx

Lines 214 to 218 in 18f248c

    
           onFocus={() => { 
        
               onFocus?.(); 
        
               autocompleteListRef?.current?.updateExternalTextInputFocus(true); 
        
               focusedSharedValue.set(true); 
        
           }}

At this point, autocompleteListRef is still null because areOptionsInitialized is false:

App/src/components/Search/SearchAutocompleteList.tsx

Line 577 in 18f248c

areOptionsInitialized && (

Due to this, updateExternalTextInputFocus is not called:

App/src/components/SelectionList/BaseSelectionList.tsx

Lines 811 to 813 in 18f248c

    
           const updateExternalTextInputFocus = useCallback((isTextInputFocused: boolean) => { 
        
               isTextInputFocusedRef.current = isTextInputFocused; 
        
           }, []);

As a result, isTextInputFocusedRef.current remains false, causing shouldSyncFocus to evaluate as true:

App/src/components/SelectionList/BaseSelectionList.tsx

Line 589 in 18f248c

shouldSyncFocus={!isTextInputFocusedRef.current && hasKeyBeenPressed.current}
This triggers the useSyncFocus hook, which blurs the input:

App/src/hooks/useSyncFocus/useSyncFocusImplementation.ts

Line 33 in 18f248c

ref.current?.focus({preventScroll: true});

Since the input is no longer focused, pressing "Enter" doesn't trigger selection logic in SearchRouter.tsx:

App/src/components/Search/SearchRouter/SearchRouter.tsx

Lines 327 to 336 in 18f248c

    
           onSubmit={() => { 
        
               const focusedOption = listRef.current?.getFocusedOption(); 
        
               if (!focusedOption) { 
        
                   submitSearch(textInputValue); 
        
                   return; 
        
               } 
        
               onListItemPress(focusedOption); 
        
           }}

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

Pass textInputRef to the SearchAutocompleteList component:

App/src/components/Search/SearchRouter/SearchRouter.tsx

Line 348 in 18f248c

<SearchAutocompleteList

  <SearchAutocompleteList ... textInputRef={textInputRef} />;

In SearchAutocompleteList.tsx, use this ref inside the onLayout handler:

App/src/components/Search/SearchAutocompleteList.tsx

Line 589 in 18f248c

onLayout={() => {

  onLayout={() => {
      ...
      ref.current?.updateExternalTextInputFocus?.(textInputRef.current.isFocused())
  }}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

Introduced a potential fallback skeleton component SearchInputSelectionWrapperSkeleton. Then conditionally render either the skeleton or the actual SearchInputSelectionWrapper based on areOptionsInitialized:

App/src/components/Search/SearchRouter/SearchRouter.tsx

Line 323 in 18f248c

<SearchInputSelectionWrapper

  areOptionsInitialized ? <SearchInputSelectionWrapper /> : <SearchInputSelectionWrapperSkeleton />;

SearchInputSelectionWrapperSkeleton can be discussed by design team.

melvin-bot · 2025-04-24T08:07:54Z

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

melvin-bot · 2025-04-24T08:07:59Z

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

mallenexpensify · 2025-04-24T08:09:47Z

@jjcoffee 👀 on the above proposals plz.

jjcoffee · 2025-04-24T08:22:30Z

@mallenexpensify Looks like @shubham1206agra was able to repro when the Needs Reproduction label was added, so he should be assigned I think!

mohit6789 · 2025-04-24T08:56:51Z

🚨 Edited by proposal-police: This proposal was edited at 2025-04-24 09:04:17 UTC.

Proposal

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

When users opens the search on chat page user can not able to open the item using keyboard navigation.

What is the root cause of that problem?

There are two issues.

Issue 1:

During first render areOptionsInitialized is false

App/src/components/Search/SearchAutocompleteList.tsx

Line 577 in 18f248c

areOptionsInitialized && (

Because of this during first render input focus list is not initialized, so input and selectionlist focus is not sync with each other.

App/src/components/Search/SearchAutocompleteInput.tsx

Lines 214 to 218 in 18f248c

    
           onFocus={() => { 
        
               onFocus?.(); 
        
               autocompleteListRef?.current?.updateExternalTextInputFocus(true); 
        
               focusedSharedValue.set(true); 
        
           }}

Issue 2:

When we use tab and press enter it can not open the selected item because we haven't passed shouldSubscribeToArrowKeyEvents in SearchAutocompleteList because of that item does not select on enter (This issue is present after first render as well)

App/src/components/Search/SearchAutocompleteList.tsx

Lines 600 to 601 in 8a9ecc6

    
           shouldSubscribeToArrowKeyEvents={shouldSubscribeToArrowKeyEvents} 
        
           disableKeyboardShortcuts={!shouldSubscribeToArrowKeyEvents}

App/src/components/SelectionList/BaseSelectionList.tsx

Line 827 in 806e231

    
           isActive: !disableKeyboardShortcuts && !disableEnterShortcut && isFocused && focusedIndex >= 0,

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

Issue 1: To fix first issue where textbox lost focus during first load we have two approaches.

Option 1 (Preffered)

We can load text input only after areOptionsInitialized we can add check here or here. We don't need to add SearchInputSelectionWrapperSkeleton since areOptionsInitialized becomes true on second render which happens very quickly (fraction of a second). Adding a skeleton would lead to undesirable flickering when opening the search dialog for the first time which may leads to regression.

Still, if we think we should show some loader then we can add condition here and show loader for entire dialog.

Options 2

Pass isInputFocused to the SearchAutocompleteList component rather than passing textInputRef. If we pass textInputRef then it makes application difficult to debug.

App/src/components/Search/SearchRouter/SearchRouter.tsx

Lines 348 to 357 in 18f248c

    
           <SearchAutocompleteList 
        
               autocompleteQueryValue={autocompleteQueryValue || textInputValue} 
        
               searchQueryItem={searchQueryItem} 
        
               getAdditionalSections={getAdditionalSections} 
        
               onListItemPress={onListItemPress} 
        
               setTextQuery={setTextAndUpdateSelection} 
        
               updateAutocompleteSubstitutions={updateAutocompleteSubstitutions} 
        
               onHighlightFirstItem={() => listRef.current?.updateAndScrollToFocusedIndex(1)} 
        
               ref={listRef} 
        
           />

 <SearchAutocompleteList
   isInputFocused={textInputRef?.current?.isFocused()}
    ...
/>

call updateExternalTextInputFocus inside the onLayout of SearchAutocompleteList. We need explicitely validate if isInputFocused is passed or not. It it does not passed it means we will not call the updateExternalTextInputFocus
https://github.com/Expensify/App/blob/main/src/components/Search/SearchAutocompleteList.tsx#L589-L592

onLayout={() => {
    setPerformanceTimersEnd();
    setIsInitialRender(false);
     if (isInputFocused !== undefined && ref && 'current' in ref) {
        ref.current?.updateExternalTextInputFocus(isInputFocused);
    }
}}

Issue 1: To Fix second issue where item does not select when user use TAB we need to pass shouldSubscribeToArrowKeyEvents in SearchAutocompleteList

App/src/components/Search/SearchRouter/SearchRouter.tsx

Line 356 in 8a9ecc6

ref={listRef}

<SearchAutocompleteList
      autocompleteQueryValue={autocompleteQueryValue || textInputValue}
      searchQueryItem={searchQueryItem}
      getAdditionalSections={getAdditionalSections}
      onListItemPress={onListItemPress}
      setTextQuery={setTextAndUpdateSelection}
      updateAutocompleteSubstitutions={updateAutocompleteSubstitutions}
      onHighlightFirstItem={() => listRef.current?.updateAndScrollToFocusedIndex(1)}
      ref={listRef}
      shouldSubscribeToArrowKeyEvents={true}
  />

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None because of ui bug

What alternative solutions did you explore? (Optional)

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.

melvin-bot · 2025-04-29T08:33:48Z

@jjcoffee Huh... This is 4 days overdue. Who can take care of this?

jjcoffee · 2025-04-29T08:52:22Z

@shubham1206agra Do you want to take this (based on you being able to repro)? Happy to review the proposals if not!

shubham1206agra · 2025-04-29T12:54:58Z

@jjcoffee I can take over this issue.

shubham1206agra · 2025-04-29T12:59:36Z

Thanks everyone for their proposals.

@thelullabyy's proposal looks good to me.

🎀👀🎀 C+ reviewed

melvin-bot · 2025-04-29T12:59:54Z

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

linhvovan29546 · 2025-04-29T13:12:44Z

@shubham1206agra Not sure if I understand correctly, but it seems we have two issues with the 'Enter' key here. The first one, as I mentioned, is that the 'Enter' key is disabled (the steps are the same as in the original post). The second issue occurs with other proposals as well — if we press 'Tab' to focus on another item, then pressing 'Enter' still doesn’t work

Screen.Recording.2025-04-29.at.20.15.55.mov

mallenexpensify · 2025-05-01T20:59:07Z

@thelullabyy can you please try to prioritize the PR? (not above any HIGH or CRITICAL issues though, this one is just annoying and there's an easy workaround)

thelullabyy · 2025-05-02T03:50:50Z

@mallenexpensify Sure, the PR will be ready today

jjcoffee · 2025-05-02T09:41:34Z

Can @shubham1206agra be assigned here please @strepanier03. Thanks!

mallenexpensify · 2025-05-05T23:10:33Z

@shubham1206agra are we waiting on you to review the PR?

Cmd+K Navigation Fails to Open Chat After Desktop Update #61311 (comment)

Assigned you to this issue and removed @jjcoffee

mvtglobally · 2025-05-10T03:34:41Z

Issue not reproducible during KI retests. (First week)

melvin-bot · 2025-05-13T17:58:07Z

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

melvin-bot · 2025-05-13T17:58:12Z

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

Cmd+K Navigation Fails to Open Chat After Desktop Update #61311

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

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

@shubham1206agra requires payment through NewDot Manual Requests
@thelullabyy requires payment automatic offer (Contributor)

melvin-bot · 2025-05-13T17:58:14Z

@shubham1206agra @strepanier03 @shubham1206agra 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]

strepanier03 · 2025-05-20T16:39:40Z

Payment summary

$250 - @shubham1206agra requires payment through NewDot Manual Requests
$250 - @thelullabyy requires payment automatic offer (Contributor)

shubham1206agra · 2025-05-20T17:04:22Z

strepanier03 · 2025-05-21T15:46:12Z

@shubham1206agra - I've made the reg test GH and removed the hold from the payment summary, feel free to request and I'll close this out.

Thanks all!

m-natarajan added Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Needs Reproduction Reproducible steps needed retest-weekly Apply this label if you want this issue tested on a Weekly basis by Applause labels Apr 23, 2025

melvin-bot bot assigned strepanier03 Apr 23, 2025

mallenexpensify added the External Added to denote the issue can be worked on by a contributor label Apr 24, 2025

melvin-bot bot changed the title ~~Cmd+K Navigation Fails to Open Chat After Desktop Update~~ [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update Apr 24, 2025

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

melvin-bot bot assigned jjcoffee Apr 24, 2025

mallenexpensify added this to #expensify-bugs Apr 24, 2025

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

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

melvin-bot bot assigned neil-marcellini Apr 29, 2025

melvin-bot bot added the Overdue label May 2, 2025

thelullabyy mentioned this issue May 2, 2025

Cmd+K Navigation Fails to Open Chat After Desktop Update #61311

Merged

51 tasks

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

mallenexpensify assigned shubham1206agra and unassigned jjcoffee May 5, 2025

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

melvin-bot bot changed the title ~~[$250] Cmd+K Navigation Fails to Open Chat After Desktop Update~~ [Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update May 13, 2025

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

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels May 20, 2025

strepanier03 changed the title ~~[Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update~~ [W4Checklist] [Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update May 20, 2025

shubham1206agra mentioned this issue May 20, 2025

fix - Web- Search - Top-most result in Recent chats is not highlighted #59709

Merged

50 tasks

strepanier03 closed this as completed May 21, 2025

github-project-automation bot moved this to Done in #expensify-bugs May 21, 2025

[W4Checklist] [Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update #60709

[W4Checklist] [Due for payment 2025-05-20] [$250] Cmd+K Navigation Fails to Open Chat After Desktop Update #60709

Comments

m-natarajan commented Apr 23, 2025 • edited by melvin-bot bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

melvin-bot bot commented Apr 23, 2025

Uh oh!

MelvinBot commented Apr 23, 2025

Uh oh!

shubham1206agra commented Apr 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linhvovan29546 commented Apr 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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 specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

Uh oh!

ishakakkad commented Apr 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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?

Solution 1

Solution 2

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

Uh oh!

thelullabyy commented Apr 23, 2025

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 specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

Uh oh!

melvin-bot bot commented Apr 24, 2025

Uh oh!

melvin-bot bot commented Apr 24, 2025

Uh oh!

mallenexpensify commented Apr 24, 2025

Uh oh!

jjcoffee commented Apr 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mohit6789 commented Apr 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposal

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

What is the root cause of that problem?

Issue 1:

Issue 2:

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

Option 1 (Preffered)

Options 2

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

Uh oh!

melvin-bot bot commented Apr 29, 2025

Uh oh!

jjcoffee commented Apr 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shubham1206agra commented Apr 29, 2025

Uh oh!

shubham1206agra commented Apr 29, 2025

Uh oh!

melvin-bot bot commented Apr 29, 2025

Uh oh!

linhvovan29546 commented Apr 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

m-natarajan commented Apr 23, 2025 •

edited by melvin-bot bot

Loading

shubham1206agra commented Apr 23, 2025 •

edited

Loading

linhvovan29546 commented Apr 23, 2025 •

edited

Loading

ishakakkad commented Apr 23, 2025 •

edited

Loading

jjcoffee commented Apr 24, 2025 •

edited

Loading

mohit6789 commented Apr 24, 2025 •

edited

Loading

jjcoffee commented Apr 29, 2025 •

edited

Loading

linhvovan29546 commented Apr 29, 2025 •

edited

Loading

strepanier03 commented May 20, 2025 •

edited

Loading

shubham1206agra commented May 20, 2025 •

edited

Loading