Reapply - Add offline search functionality for addresses #43011

pac-guerreiro · 2024-06-03T20:13:21Z

Details

Add offline search functionality for addresses

Fixed Issues

$ #30123
PROPOSAL: #30123 (comment)

Tests

Go to staging.new.expensify.com
Click on FAB> Submit Expense > Distance tab
Select different locations several times
Go offline
Select Start point
Enter any letter into search field and check if search result will update according to entered letter

Offline tests

Same as above

QA Steps

Same as above

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android.-.Native.mp4

Android: mWeb Chrome

Android.-.Web.mp4

iOS: Native

iOS.-.Native.mp4

iOS: mWeb Safari

iOS.-.Web.mp4

MacOS: Chrome / Safari

MacOS.-.Web.mp4

MacOS: Desktop

MacOS.-.Desktop.mp4

…ssues/30123" This reverts commit ad20280.

melvin-bot · 2024-06-03T20:13:25Z

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

melvin-bot · 2024-06-03T20:13:26Z

@dubielzyk-expensify @eVoloshchak One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

pac-guerreiro · 2024-06-03T20:22:47Z

@neil-marcellini @eVoloshchak @arosiclair

Here is the fixed PR, but someone from QA should test this because I'm not able to test everything!

I applied the special logic to hide the submit button in the flow, to make sure that the waypoint list would fit the available screen space, when the keyboard showed.

At the time I investigated the google autocomplete component and I didn't find a way to make it work with our form container, but I'll take a look into it again.

Meanwhile if you have a different idea, please let me know so I can apply it here 😄

dubielzyk-expensify · 2024-06-05T09:24:58Z

From a visual perspective this isn't changing anything so as long as the QA holds up for the test cases, then that's fine 👍

pac-guerreiro · 2024-06-07T13:28:59Z

@neil-marcellini @eVoloshchak @arosiclair

Still waiting on reviews here 😄

neil-marcellini

Please include the following test to ensure that we fixed this bug [HOLD for payment 2024-06-11] [HOLD for payment 2024-06-06] IOU - Save button is not above keyboard when waypoint input is in focus

Precondition:

Recent destinations list has a few addresses

Go offline
Go to FAB > Submit expense > Distance
Tap Start
Tap on the input
Verify that the Save button does not appear above the keyboard
enter some text and hit done on the keyboard
Verify that the Save button appears again
Tap into the input and clear the text
Tap system back button (or swipe) to dismiss the keyboard while the input is still in focus
Verify that the save button appears

I'm actually kind of torn on point 6. The user can tap out of the input when they're done, or hit "done" on the Android keyboard, and then the save button will show, but it would be a bit more clear to always render the save button. Also, it would be good to check if iOS shows a "Done" button or instead "Enter" which is confusing. Do we really need to hide the save button for extra space? We can discuss on Slack if that's easier. What do you think @arosiclair?

Also, please include tests for all the regressions that happened last time.

The code looks great, except one tiny TS change.

src/pages/iou/request/step/IOURequestStepWaypoint.tsx

src/components/AddressSearch/index.tsx

src/components/AddressSearch/listViewOverflow/index.native.ts

src/hooks/useSubmitButtonVisibility.ts

arosiclair · 2024-06-10T14:01:55Z

Do we really need to hide the save button for extra space? We can discuss on Slack if that's easier. What do you think @arosiclair?

Yeah I'm also having this question now. Based on this frame from the Android test I would say it's fine to just always show the save button. Especially since you can still easily scroll the results list:

eVoloshchak · 2024-06-12T11:11:38Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

24-07-07-23-48-41.mp4

Android: mWeb Chrome

Screen.Recording.2024-07-07.at.23.36.47.mov

iOS: Native

Screen.Recording.2024-07-07.at.23.35.18.mov

iOS: mWeb Safari

Screen.Recording.2024-07-07.at.23.33.19.mov

MacOS: Chrome / Safari

Screen.Recording.2024-07-07.at.23.29.16.mov

MacOS: Desktop

Screen.Recording.2024-07-07.at.23.31.12.mov

eVoloshchak · 2024-06-12T11:21:04Z

src/components/AddressSearch/index.tsx

-                            listView: [StyleUtils.getGoogleListViewStyle(displayListViewBorder), styles.overflowAuto, styles.borderLeft, styles.borderRight, !isFocused && {height: 0}],
+                            listView: [
+                                StyleUtils.getGoogleListViewStyle(displayListViewBorder),
+                                listViewOverflow,


Given the recent changes, is this style still needed?

@eVoloshchak good point! I just removed this 😄 Thanks!

pac-guerreiro · 2024-06-28T11:59:33Z

@eVoloshchak I think I finally managed to find a solution that works! Can you try it?

neil-marcellini · 2024-07-01T15:41:55Z

Gentle bump @eVoloshchak

eVoloshchak

UI is looking good, awesome job!

There's a small offline bug though:

Go offline
Click on FAB> Submit Expense > Distance tab
Select a start location
While on Distance tab, with start location selected, click on location once again to select a new start point
Notice that only some predefined places are shown (only those that satisfy the search query for currently selected start point)

Screen.Recording.2024-07-02.at.16.37.58.mov

It should show all of the predefined places, same as when online

Screen.Recording.2024-07-02.at.16.37.22.mov

pac-guerreiro · 2024-07-02T17:06:46Z

@eVoloshchak just pushed a fix for it! Thanks 😄

eVoloshchak

@pac-guerreiro, offline search is broken by 785a45f

Screen.Recording.2024-07-03.at.21.14.44.mov

# Conflicts: # src/CONST.ts

This reverts commit 785a45f.

pac-guerreiro · 2024-07-04T18:52:11Z

@eVoloshchak now it should work properly! 😄

eVoloshchak

LGTM!

neil-marcellini

Looks good, thanks for sticking with this one guys!

OSBotify · 2024-07-08T21:39:53Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-07-10T11:19:08Z

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 9.0.6-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	failure ❌
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-10T11:36:22Z

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 9.0.6-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-11T10:16:37Z

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	failure ❌
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-11T10:36:13Z

🚀 Cherry-picked to staging by https://github.com/Julesssss in version: 9.0.6-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

Krishna2323 · 2024-07-11T21:17:25Z

src/pages/iou/request/step/IOURequestStepWaypoint.tsx

                // that the google autocomplete component expects for it's "predefined places" feature.
                selector: (waypoints) =>
-                    (waypoints ? waypoints.slice(0, 5) : []).map((waypoint) => ({
+                    (waypoints ? waypoints.slice(0, CONST.RECENT_WAYPOINTS_NUMBER as number) : []).map((waypoint) => ({


@neil-marcellini @arosiclair @eVoloshchak, this has caused a regression. Can you pls confirm whats the expected fix for that? I think we can slice the predefinedPlaces array to only show 5 items at a time. It will be still able to search and find option from all the 20 options, we will just slice the array for the UI.

Not a bug, it's working as desired as explained in that regression issue here

OSBotify · 2024-07-15T20:18:17Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.6-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2024-07-17T00:17:43Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

ntdiary · 2024-10-16T14:38:15Z

src/components/AddressSearch/index.tsx

@@ -304,10 +322,16 @@ function AddressSearch(
        };
    }, []);

+    const filteredPredefinedPlaces = useMemo(() => {


Coming from #48643. If user is online, the filtered predefined places will briefly appear before the server returns the result. :)

pac-guerreiro added 3 commits June 3, 2024 20:26

Reapply "Merge pull request Expensify#35045 from callstack-internal/i…

8ffcb6b

…ssues/30123" This reverts commit ad20280.

fix: unreachable form inputs

e81675e

chore: disable typescript rule for constant

d039eb0

pac-guerreiro requested review from a team as code owners June 3, 2024 20:13

melvin-bot bot requested review from dubielzyk-expensify and eVoloshchak and removed request for a team June 3, 2024 20:13

pac-guerreiro changed the title ~~Add offline search functionality for addresses~~ Reapply - Add offline search functionality for addresses Jun 3, 2024

neil-marcellini self-requested a review June 7, 2024 16:56

neil-marcellini requested changes Jun 7, 2024

View reviewed changes

src/pages/iou/request/step/IOURequestStepWaypoint.tsx Outdated Show resolved Hide resolved

neil-marcellini requested a review from arosiclair June 7, 2024 17:08

arosiclair requested changes Jun 10, 2024

View reviewed changes

src/components/AddressSearch/index.tsx Outdated Show resolved Hide resolved

src/components/AddressSearch/listViewOverflow/index.native.ts Outdated Show resolved Hide resolved

src/hooks/useSubmitButtonVisibility.ts Outdated Show resolved Hide resolved

pac-guerreiro added 4 commits June 11, 2024 08:56

Merge branch 'main' into issues/30123

89492f6

Merge branch 'main' into issues/30123

cab7692

Merge branch 'main' into issues/30123

7257198

fix: hiding submit button on address search screen

838218d

eVoloshchak reviewed Jun 12, 2024

View reviewed changes

pac-guerreiro added 2 commits June 12, 2024 13:48

refactor: remove unnecessary code and comments

6b11184

Merge branch 'main' into issues/30123

ea52a61

pac-guerreiro requested review from eVoloshchak, neil-marcellini and arosiclair June 12, 2024 15:08

eVoloshchak suggested changes Jul 2, 2024

View reviewed changes

pac-guerreiro added 2 commits July 2, 2024 17:15

Merge branch 'main' into issues/30123

27c9233

fix: predefined places being filtered in offline mode

785a45f

pac-guerreiro requested a review from eVoloshchak July 2, 2024 17:08

eVoloshchak reviewed Jul 3, 2024

View reviewed changes

pac-guerreiro added 3 commits July 4, 2024 19:45

Merge branch 'main' into issues/30123

4920a65

# Conflicts: # src/CONST.ts

Revert "fix: predefined places being filtered in offline mode"

0b5bbe3

This reverts commit 785a45f.

fix: address search not showing recent waypoints while offline

363ab6f

pac-guerreiro requested a review from eVoloshchak July 4, 2024 18:52

eVoloshchak approved these changes Jul 7, 2024

View reviewed changes

melvin-bot bot requested a review from neil-marcellini July 7, 2024 21:58

neil-marcellini approved these changes Jul 8, 2024

View reviewed changes

neil-marcellini merged commit 29e8df5 into Expensify:main Jul 8, 2024
15 checks passed

mallenexpensify mentioned this pull request Jul 9, 2024

Distance offline - Can't delete red dot Error on the request preview in the expense report #38392

Closed

6 tasks

github-actions bot mentioned this pull request Jul 10, 2024

Deploy Checklist: New Expensify 2024-07-10 #45144

Closed

Krishna2323 mentioned this pull request Jul 11, 2024

[$250] Distance - Recent destination list shows more than 5 destinations #45241

Closed

6 tasks

Krishna2323 reviewed Jul 11, 2024

View reviewed changes

ntdiary reviewed Oct 16, 2024

View reviewed changes

ntdiary mentioned this pull request Oct 17, 2024

[$250] Android - Distance - Previous waypoints displayed for a second before new suggestions appear #48643

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Reapply - Add offline search functionality for addresses #43011

Reapply - Add offline search functionality for addresses #43011

pac-guerreiro commented Jun 3, 2024 •

edited

Loading

melvin-bot bot commented Jun 3, 2024

melvin-bot bot commented Jun 3, 2024

pac-guerreiro commented Jun 3, 2024

dubielzyk-expensify commented Jun 5, 2024

pac-guerreiro commented Jun 7, 2024

neil-marcellini left a comment

arosiclair commented Jun 10, 2024

eVoloshchak commented Jun 12, 2024 •

edited

Loading

eVoloshchak Jun 12, 2024

pac-guerreiro Jun 12, 2024

pac-guerreiro commented Jun 28, 2024

neil-marcellini commented Jul 1, 2024

eVoloshchak left a comment

pac-guerreiro commented Jul 2, 2024

eVoloshchak left a comment

pac-guerreiro commented Jul 4, 2024

eVoloshchak left a comment

neil-marcellini left a comment

OSBotify commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 11, 2024

Krishna2323 Jul 11, 2024

neil-marcellini Jul 12, 2024

OSBotify commented Jul 15, 2024

OSBotify commented Jul 17, 2024

ntdiary Oct 16, 2024 •

edited

Loading

Reapply - Add offline search functionality for addresses #43011

Reapply - Add offline search functionality for addresses #43011

Conversation

pac-guerreiro commented Jun 3, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 3, 2024

melvin-bot bot commented Jun 3, 2024

pac-guerreiro commented Jun 3, 2024

dubielzyk-expensify commented Jun 5, 2024

pac-guerreiro commented Jun 7, 2024

neil-marcellini left a comment

Choose a reason for hiding this comment

arosiclair commented Jun 10, 2024

eVoloshchak commented Jun 12, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

eVoloshchak Jun 12, 2024

Choose a reason for hiding this comment

pac-guerreiro Jun 12, 2024

Choose a reason for hiding this comment

pac-guerreiro commented Jun 28, 2024

neil-marcellini commented Jul 1, 2024

eVoloshchak left a comment

Choose a reason for hiding this comment

pac-guerreiro commented Jul 2, 2024

eVoloshchak left a comment

Choose a reason for hiding this comment

pac-guerreiro commented Jul 4, 2024

eVoloshchak left a comment

Choose a reason for hiding this comment

neil-marcellini left a comment

Choose a reason for hiding this comment

OSBotify commented Jul 8, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 10, 2024

OSBotify commented Jul 11, 2024

OSBotify commented Jul 11, 2024

Krishna2323 Jul 11, 2024

Choose a reason for hiding this comment

neil-marcellini Jul 12, 2024

Choose a reason for hiding this comment

OSBotify commented Jul 15, 2024

OSBotify commented Jul 17, 2024

ntdiary Oct 16, 2024 • edited Loading

Choose a reason for hiding this comment

pac-guerreiro commented Jun 3, 2024 •

edited

Loading

eVoloshchak commented Jun 12, 2024 •

edited

Loading

ntdiary Oct 16, 2024 •

edited

Loading