Fix the new message button doesn't work on some comment linkings #46627

tsa321 · 2024-08-01T00:27:29Z

Details

Fixed Issues

$ #45004
PROPOSAL: #45004 (comment)

Tests

Go to a chat with 200 - 210 messages
Copy the link of the 70th comment and send it
Copy the link of the 140th comment and send it
Go to troubleshoot and clear cache and restart
Click on the first link sent on step 2
Click on the "New message" badge that appeared at the top of the chat
Confirm the page scrolls to the bottom of the comment history
Click on the second link sent on step 3.
Click on the "New message" badge once again
Confirm the page scrolls to the bottom of the comment history

Verify that no errors appear in the JS console

Offline tests

QA Steps

Go to a chat with 200 - 210 messages
Copy the link of the 70th comment and send it
Copy the link of the 140th comment and send it
Go to troubleshoot and clear cache and restart
Click on the first link sent on step 2
Click on the "New message" badge that appeared at the top of the chat
Confirm the page scrolls to the bottom of the comment history
Click on the second link sent on step 3.
Click on the "New message" badge once again
Confirm the page scrolls to the bottom of the comment history

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android-native-d.mp4

Android: mWeb Chrome

android-mweb_d.mp4

iOS: Native

ios-native_d.mp4

iOS: mWeb Safari

ios-msfari_d.mp4

MacOS: Chrome / Safari

macos-web-d.mp4

MacOS: Desktop

macos-desktop_d.mp4

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

melvin-bot · 2024-08-01T00:27:34Z

@s77rt Please 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]

tsa321 · 2024-08-01T00:30:14Z

@s77rt I am not sure if I should include my proposed fix for paginationUtils. Should I include it or not?

s77rt · 2024-08-01T07:24:15Z

@tsa321 Is the pagination bug still reproducible? If so can you please add reproduction steps?

s77rt · 2024-08-01T07:33:05Z

@tsa321 It seems that something broke

Screen.Recording.2024-08-01.at.8.31.50.AM.mov

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 · 2024-08-01T16:14:31Z

@s77rt Thanks for the review.

For the last part of the video, where the page doesn’t scroll to the last message, we need to include the pageUtils fix.

Regarding the flicker of the loading skeleton, could you provide more details about the linked message, such as how many positions up from the last message it is? Also, could you reproduce the issue in the main branch?
I’m having difficulty reproducing the flicker issue, but found another bug instead. I don't know if it is related:

macos-web-d.mp4

I will try to submit new commit tomorrow.
Thank you...

s77rt · 2024-08-01T17:20:40Z

The latest commit didn't fix the reported but and now the "New message" button is not visible

Screen.Recording.2024-08-01.at.6.16.02.PM.mov

tsa321 · 2024-08-01T22:53:09Z

@s77rt, since the current commit is minimal, could you check if the following three bugs are also present in the main branch by manually reverting my changes?

The loading skeleton flicker (it disappears after I merge with the main branch, right? based on your last video).
The scrolling-to-last-message bug.
The new message button not appearing (I think this might be a bug in the main branch).

Also, is it possible for me to get the exported Onyx data?

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

s77rt · 2024-08-02T13:38:02Z

@tsa321 Those bugs appear to be on main as well and must be fixed as they block testing the original bug

…types and lints Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 · 2024-08-02T15:41:46Z

@s77rt I have tried to fix the bugs in the last commit. Although there is a GitHub check error, could you please re-test it

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

s77rt · 2024-08-03T11:27:28Z

src/pages/home/ReportScreen.tsx

@@ -95,7 +96,8 @@ function getParentReportAction(parentReportActions: OnyxEntry<OnyxTypes.ReportAc
    return parentReportActions[parentReportActionID ?? '0'];
 }

-function ReportScreen({route, currentReportID = '', navigation}: ReportScreenProps) {
+function ReportScreen({currentReportID = '', navigation}: ReportScreenProps) {
+    const route = useRoute<RouteProp<AuthScreensParamList, typeof SCREENS.REPORT>>();


Why is this change necessary?

@s77rt When a user clicks the same linked message twice (when the current URL path and the clicked link are the same), the useRoute returns a different object (different reference to object), but it has the same content as the previous one. However, the route property of the ReportScreen remains the same in both content and object reference. Consequently, the second click does not work (won't re-render) using route property of ReportScreen. Here is the video:

using route property of report screen:

usginRouteProperty.mp4

using useRoute:

usingUseRoute.mp4

But this is already working on main, what broke it?

Screen.Recording.2024-08-04.at.5.14.09.PM.mov

@s77rt Because I am fixing this bug, I am using the same source of route in ReportScreen, ReportActionsView, and ReportActionsList.

In your video, the bug does not appear in the main branch because ReportActionsView is using useRoute.

You can reproduce this bug by reverting these two lines in my changes, meaning by using the route property of ReportScreen instead of useRoute.

@tsa321 Can you please clarify the solution independently for those two bugs:

Not showing "new message" button

Not navigating on clicking same report action link

(Also please merge main)

s77rt · 2024-08-03T11:29:11Z

src/libs/PaginationUtils.ts

@@ -124,7 +124,7 @@ function mergeAndSortContinuousPages<TResource>(sortedItems: TResource[], pages:
    const result = [sortedPages[0]];
    for (let i = 1; i < sortedPages.length; i++) {
        const page = sortedPages[i];
-        const prevPage = sortedPages[i - 1];
+        const prevPage = result?.at(-1) ?? sortedPages[i - 1];


Why do we fallback to sortedPages[i - 1]?

Actually I am trying to fix a type-checking error. result?.at(-1) gives a type-checking error. Should I use result[result?.length - 1] instead?

prevPage is expected to be undefined at first, no need for the fallback

Alright, since result?.at(-1) fails the type check, I will use result[result?.length - 1] instead.

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 · 2024-08-05T00:27:10Z

@tsa321 Is the pagination bug still reproducible? If so can you please add reproduction steps?

I missed this comment.

To reproduce the issue, the steps are:

Clear the Onyx cache.
Click a link to a message 170 messages above the latest message, then click the New Message button.
Click a link to a message 60 messages above the latest message, then click the New Message button.
Notice that after clicking the New Message button, the message does not immediately appear to be the latest message.

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

s77rt · 2024-08-05T13:15:49Z

src/libs/PaginationUtils.ts

@@ -124,7 +124,7 @@ function mergeAndSortContinuousPages<TResource>(sortedItems: TResource[], pages:
    const result = [sortedPages[0]];
    for (let i = 1; i < sortedPages.length; i++) {
        const page = sortedPages[i];
-        const prevPage = sortedPages[i - 1];
+        const prevPage = result[result.length - 1];


prepage (result[result.length - 1]) could be same as page if the result contains only one page

@s77rt What? I don't understand. Could you elaborate please?
Do you mean when the sortedPages.length is 1. If it is 1 it won't even enter the for loop.

If result length is 1, then:
page = sortedPages[0]
and
prevPage = sortedPages[0]

page is same as prevPage which is misleading and could cause bugs

@s77rt Maybe I still don't understand.
The i in the for loop starts at 1, not 0, so page = sortedPages[0] is not possible. Consequently, page and prevPage won't be the same.

Am I missing something?

const prevPage = result[result.length - 1]; Here I am using the last updated page of result and not the sortedPages.
The end of result could be only 1 continuous page for for example 10 pages in sortedPages. Because the function merge the pages into one continuous page.

Ah right! my bad

s77rt · 2024-08-05T13:28:51Z

src/pages/home/ReportScreen.tsx

@@ -95,7 +96,8 @@ function getParentReportAction(parentReportActions: OnyxEntry<OnyxTypes.ReportAc
    return parentReportActions[parentReportActionID ?? '0'];
 }

-function ReportScreen({route, currentReportID = '', navigation}: ReportScreenProps) {
+function ReportScreen({currentReportID = '', navigation}: ReportScreenProps) {
+    const route = useRoute<RouteProp<AuthScreensParamList, typeof SCREENS.REPORT>>();


@tsa321 Can you please clarify the solution independently for those two bugs:

Not showing "new message" button

Not navigating on clicking same report action link

(Also please merge main)

tsa321 · 2024-08-05T14:14:23Z

@s77rt for bug:

Not showing "new message" button. Fix: use one source of the route from in ReportScreen , ReportActionsView and ReportActionsList. So the components will synchronized when the route changes.
Not navigating on clicking same report action link. Fix: Must use useRoute to get the value of route in ReportScreen. Using the route property of ReportScreen will cause this bug to persist.

tsa321 · 2024-08-06T16:29:42Z

@s77rt Is it also reproducible in main?
Also could you reproduce it before I revert the route scheme?
I cannot reproduce that issue like I said in my previous comment, so it will be hard to figure it out.

s77rt · 2024-08-06T21:23:59Z

@tsa321 I can reproduce on main and also before the routes changes revert.

tsa321 · 2024-08-06T22:23:23Z

@s77rt Should I fix that issue as well? I need more information to reproduce the bug.

s77rt · 2024-08-07T03:47:32Z

@tsa321 It would be better if we can get this fixed or at least find what went wrong. Can't you reproduce the bug on main? There are no specific steps besides clicking on the report action link

tsa321 · 2024-08-07T03:59:13Z

@s77rt I cannot reproduce the issue, so it will be really difficult to figure out. Is your connection slow? It might be related to isOffline. Could you console log isOffline in ReportScreen?

I'm just guessing here because I can't reproduce the issue. Could you provide more information: which counts from the last message are the first and second linked messages, and how many messages are in the report?

Or if you could invite me to the room or make it public report...

Alternatively, we could address this in a follow-up PR.

s77rt · 2024-08-07T09:58:57Z

@tsa321 Let's not block on that.

Click on the second link sent on step 5.

This should refer to step 3

tsa321 · 2024-08-07T10:17:15Z

@s77rt I have edited the test step.

s77rt · 2024-08-07T10:17:17Z

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

android.mov

Android: mWeb Chrome

mweb-chrome.mov

iOS: Native

ios.mov

iOS: mWeb Safari

mweb-safari.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

s77rt · 2024-08-07T10:18:46Z

On Android the new message button does not scroll to the bottom

android-bug.mov

tsa321 · 2024-08-07T13:09:38Z

@s77rt, on Android, this issue occurs in the main branch on many comment linkings. Even without clearing the Onyx cache (cached messages exist) , the new message button fails to display the newest messages correctly.

Before merging the main branch, everything worked as expected, as shown in the Android video test I uploaded. However, after merging, the same link I used for testing fails to display the newest message.
Additionally, when tapping on the comment link, the app does not display the linked message correctly.

tsa321 · 2024-08-07T14:08:48Z

@s77rt update:

Removing this useEffect:

App/src/components/FlatList/index.android.tsx

Lines 28 to 32 in 65bca91

    
           useFocusEffect( 
        
               useCallback(() => { 
        
                   onScreenFocus(); 
        
               }, [onScreenFocus]), 
        
           );

works as expected for me.

s77rt · 2024-08-07T19:27:00Z

@tsa321 That code was there for a while, it can't be the culprit. Can you try find the offending PR or the root cause. Also try disable strict mode and test on production

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 · 2024-08-08T10:20:39Z

src/components/FlatList/index.android.tsx

+        setScrollPosition(undefined);
+        return () => setScrollPosition(undefined);
+    },[])
+


The CustomFlatList component tries to scroll the flat list back using useFocusEffect below. However, when we open or click on a comment link, we don't need to restore the scroll position. Therefore, we must reset the last scroll position to undefined on mount and unmount.

tsa321 · 2024-08-08T10:25:03Z

src/components/FlatList/index.android.tsx

 import type {FlatListProps, NativeScrollEvent, NativeSyntheticEvent} from 'react-native';
 import {FlatList} from 'react-native';
 import {ActionListContext} from '@pages/home/ReportScreenContext';

 // FlatList wrapped with the freeze component will lose its scroll state when frozen (only for Android).
 // CustomFlatList saves the offset and use it for scrollToOffset() when unfrozen.
 function CustomFlatList<T>(props: FlatListProps<T>, ref: ForwardedRef<FlatList>) {
-    const {scrollPosition, setScrollPosition} = useContext(ActionListContext);
+    const {setScrollPosition, getScrollPosition} = useContext(ActionListContext);



I am replacing scrollPosition with getScrollPosition because scrollPosition is a state in ReportScreen and does not represent the last value here. Using useState for scroll position also causes the ReportScreen to re-render unnecessarily when user stop scrolling the flat list.
I have verified that scrollPosition is only used in here.
For more details, see ReportScreen.

tsa321 · 2024-08-08T10:26:29Z

src/pages/home/ReportScreen.tsx

+
+    const getScrollPosition = useCallback(() => {
+        return scrollPosition;
+    }, []);



I am replacing scrollPosition with getScrollPosition because scrollPosition is a state in ReportScreen and the setScrollPosition will cause re-render of reportscreen unnecessarily and cause the flatlist to jumping around. Using useState for scroll position also causes the ReportScreen to re-render unnecessarily when user stop scrolling the flat list.

tsa321 · 2024-08-08T10:27:04Z

@s77rt I have fixed the issue please review before I am fixing the type or lint errors.

s77rt · 2024-08-08T15:28:56Z

@tsa321 Before going with a solution, we need to find the root cause and since this broke recently it's better to find the offending PR first

tsa321 · 2024-08-08T15:48:26Z

I haven’t been able to find it. Should we wait for it to be fixed in the main branch, or do you have another suggestion? I'm fine with either option.

s77rt · 2024-08-09T13:09:51Z

@tsa321 Can you revert the latest changes and merge main. I think it would be better to have this handled separately

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 · 2024-08-10T23:57:45Z

@s77rt I have reverted the last changes and merged main

s77rt

on Android it's partially working as expected but that seems due to another cause. Let's not block on that

android.mov

OSBotify · 2024-08-12T00:31:14Z

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

Beamanator · 2024-08-14T20:13:26Z

FYI I believe this was deployed to prod yesterday, from this checklist - #47219

Fix the new message button doesn't work for some comment linkings

00a7bed

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 requested a review from a team as a code owner August 1, 2024 00:27

melvin-bot bot requested review from s77rt and removed request for a team August 1, 2024 00:27

tsa321 mentioned this pull request Aug 1, 2024

[HOLD for payment 2024-08-27] [$250] Clicking on new message doesn't navigate to the last message for 2nd comment link #45004

Closed

6 tasks

tsa321 added 2 commits August 1, 2024 20:17

Merge branch 'main' into fixNwMessageBtnCmntLnkng

69ce490

Fix pagination util prev page

4987917

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Using one source of route for report screen, view and list

76f9489

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 added 4 commits August 2, 2024 21:01

using one source of route in report screen, view and list and fixees …

7036096

…types and lints Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Merge branch 'main' into fixNwMessageBtnCmntLnkng

4b4b369

revert index of linked action search

3235453

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Fix typechek error

ceae85f

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Fix perf-test error

a9d1374

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

bernhardoj mentioned this pull request Aug 3, 2024

Fix chat doesn't scroll to bottom when adding message while linked to an old action #46724

Merged

50 tasks

s77rt suggested changes Aug 3, 2024

View reviewed changes

Change method to get last item of result

02fca25

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Fix lint

da00fa5

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

s77rt suggested changes Aug 5, 2024

View reviewed changes

Merge branch 'main' into fixNwMessageBtnCmntLnkng

19844ab

Fix commment linking jumping around and new message button in android

c498c92

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

tsa321 commented Aug 8, 2024

View reviewed changes

tsa321 added 2 commits August 11, 2024 06:46

Revert changes

0993bd4

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

Merge main

c3bc9d1

Signed-off-by: Tsaqif <tsaiinkwa@yahoo.com>

s77rt approved these changes Aug 11, 2024

View reviewed changes

melvin-bot bot requested a review from francoisl August 11, 2024 18:57

francoisl approved these changes Aug 12, 2024

View reviewed changes

francoisl merged commit e7fe622 into Expensify:main Aug 12, 2024
16 checks passed

github-actions bot mentioned this pull request Aug 12, 2024

Deploy Checklist: New Expensify 2024-08-12 #47219

Closed

90 tasks

Fix the new message button doesn't work on some comment linkings #46627

Fix the new message button doesn't work on some comment linkings #46627

Conversation

tsa321 commented Aug 1, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 1, 2024

tsa321 commented Aug 1, 2024

s77rt commented Aug 1, 2024

s77rt commented Aug 1, 2024

tsa321 commented Aug 1, 2024 • edited Loading

s77rt commented Aug 1, 2024

tsa321 commented Aug 1, 2024 • edited Loading

s77rt commented Aug 2, 2024

tsa321 commented Aug 2, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tsa321 Aug 5, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tsa321 commented Aug 5, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tsa321 Aug 5, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tsa321 commented Aug 5, 2024

tsa321 commented Aug 6, 2024

s77rt commented Aug 6, 2024

tsa321 commented Aug 6, 2024

s77rt commented Aug 7, 2024

tsa321 commented Aug 7, 2024 • edited Loading

s77rt commented Aug 7, 2024

tsa321 commented Aug 7, 2024

s77rt commented Aug 7, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

s77rt commented Aug 7, 2024

tsa321 commented Aug 7, 2024

tsa321 commented Aug 7, 2024 • edited Loading

s77rt commented Aug 7, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tsa321 commented Aug 8, 2024

s77rt commented Aug 8, 2024

tsa321 commented Aug 8, 2024 • edited Loading

s77rt commented Aug 9, 2024

tsa321 commented Aug 10, 2024

s77rt left a comment

Choose a reason for hiding this comment

OSBotify commented Aug 12, 2024

Beamanator commented Aug 14, 2024

tsa321 commented Aug 1, 2024 •

edited

Loading

tsa321 commented Aug 1, 2024 •

edited

Loading

tsa321 commented Aug 1, 2024 •

edited

Loading

tsa321 Aug 5, 2024 •

edited

Loading

tsa321 Aug 5, 2024 •

edited

Loading

tsa321 commented Aug 7, 2024 •

edited

Loading

s77rt commented Aug 7, 2024 •

edited

Loading

tsa321 commented Aug 7, 2024 •

edited

Loading

tsa321 commented Aug 8, 2024 •

edited

Loading