Fix: On tapping device back button to close troubleshoot box from LHN, navigated out of site #58608

nyomanjyotisa · 2025-03-18T02:21:39Z

Explanation of Change

Fixed Issues

$ #58383
PROPOSAL: #58383 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Open the test tool modal with Command + D or a four-finger gesture on mobile.
Tap the browser back button or the device's back button.
Verify that the test tool modal is closed.
Open the search modal with Command + K or tap the search icon at the top.
Tap the browser back button or the device's back button.
Verify that the search modal is closed.

Verify that no errors appear in the JS console

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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 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 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.ts 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 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.
I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
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-mWeb.Chrome.mp4

iOS: Native

iOS-Native.mp4

iOS: mWeb Safari

iOS-mWeb.Safari.mp4

MacOS: Chrome / Safari

MacOS-Chrome.mp4

MacOS: Desktop

MacOS-Desktop.mp4

…, navigated out of site

melvin-bot · 2025-03-18T04:42:16Z

@hungvu193 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]

hungvu193 · 2025-03-18T07:31:16Z

Everything is working well 🎉. The only concern here is that after the TestToolModal or SearchDialog are dismissed, the forward button does nothing, it's because we pushed an empty URL state here, to pop it when the user presses back later. And then when the modal hides, we pop that empty state here, which makes forward enabled.

App/src/components/Modal/index.tsx

Lines 26 to 28 in ece826f

    
           if ((window.history.state as WindowState)?.shouldGoBack) { 
        
               window.history.back(); 
        
           }

I think that's the reason why we only use shouldHandleNavigationBack with mobile browser:

Screen.Recording.2025-03-18.at.14.18.28.mov

hungvu193 · 2025-03-19T15:47:06Z

What do you think about the comment about? Do you have any idea to fix it?

nyomanjyotisa · 2025-03-20T02:13:11Z

I noticed that the shouldHandleNavigationBack flag is also set to true in several modal

Should we address this issue in the current PR or handle it in a separate one?

I think we could add a new function to manage the forward click, which would reopen the modal. Will check further if we need to handle that case on this PR

hungvu193 · 2025-03-20T02:15:03Z

If a generic solution can be applied for all other places then I think Yes.

nyomanjyotisa · 2025-03-21T06:25:25Z

Alright, I will look into that issue further. I'll let you know if we can use that approach

hungvu193 · 2025-03-28T08:01:44Z

Any luck? @nyomanjyotisa

hungvu193 · 2025-03-29T09:17:01Z

I'm thinking about the modal screen:
https://reactnavigation.org/docs/modal/

I think we also have a plan to convert all the current modal to screen (not sure what the latest decision is), but let me know your opinion.

nyomanjyotisa · 2025-04-01T01:32:17Z

Unfortunately, I encountered some issues when implementing the approach to re-open the modal when the forward button is clicked

I'm thinking about the modal screen:
https://reactnavigation.org/docs/modal/

I think we also have a plan to convert all the current modal to screen (not sure what the latest decision is), but let me know your opinion.

Sure, let me try this approach

hungvu193 · 2025-04-08T08:20:52Z

Any updates here? Let me know anything that I can help

hungvu193 · 2025-04-11T08:04:23Z

Still in progress.

hungvu193 · 2025-04-14T08:18:04Z

Hey @nyomanjyotisa, any updates here?

If the modal screen solution doesn't work and you don't have any other solution to resolve the issue, then I think we should open this issue for proposals again.

nyomanjyotisa · 2025-04-15T10:29:28Z

@hungvu193 Sorry for the slow update here, could you please check the updated code? Thanks!

hungvu193 · 2025-04-15T10:30:33Z

Can you also update all the screenshots/videos please?

nyomanjyotisa · 2025-04-29T05:23:33Z

Sure, I'll create a Slack post about overlay on native as soon as possible

hungvu193 · 2025-05-05T03:19:45Z

Checked on main, same behavior we can go ahead with current solution

I’m not sure whether CMD+K in the native app should open the Search modal, but it didn’t open anything in the latest main The same goes for CMD+D, it didn’t open the Test Tools modal in the latest main

OK, let me investigate this one. In the meantime, can you create a slack post to get help with the overlay on native please?

hungvu193 · 2025-05-05T03:22:35Z

src/libs/Navigation/AppNavigator/PublicScreens.tsx

@@ -67,6 +68,11 @@ function PublicScreens() {
                component={PublicRightModalNavigator}
                options={rootNavigatorScreenOptions.rightModalNavigator}
            />
+            <RootStack.Screen
+                name={NAVIGATORS.TEST_TOOLS_MODAL_NAVIGATOR}
+                options={rootNavigatorScreenOptions.basicModalNavigator}


We can create a custom screen options here with the native option for the native to enable the overlay:

Suggested change

options={rootNavigatorScreenOptions.basicModalNavigator}

options={{

...rootNavigatorScreenOptions.basicModalNavigator,

native: {

contentStyle: {

backgroundColor: theme.overlay

}

}

}}

We can confirm the backdrop color with design team later:

Screen.Recording.2025-05-05.at.10.22.22.mov

Now we have another thing to address. Click on overlay to dismiss the modal. You can see the references here:
https://reactnavigation.org/docs/stack-navigator/#transparent-modals

If you want to further customize how the dialog animates, or want to close the screen when tapping the overlay etc., you can use the useCardAnimation hook to customize elements inside your screen.

I've updated the PR and addressed this issue as well

Click on overlay to dismiss the modal

Could you please review it again?

hungvu193 · 2025-05-07T02:30:55Z

src/libs/Navigation/AppNavigator/AuthScreens.tsx

+                            contentStyle: {
+                                backgroundColor: theme.overlay,
+                            },
+                            animation: InternalPlatformAnimations.SLIDE_FROM_BOTTOM,


Let's use FADE here for smoother animation

Suggested change

animation: InternalPlatformAnimations.SLIDE_FROM_BOTTOM,

animation: InternalPlatformAnimations.FADE,

hungvu193 · 2025-05-07T02:34:44Z

Hi @Expensify/design team, we plan to migrate the current TestTools modal to Modal Screen. Could you please review the UI below and give us feedback? Thank you

With slide from bottom animation:

push.from.bottom.mov

With fade animation:

fade.mov

Chrome:

Screen.Recording.2025-05-07.at.09.34.10.mov

dubielzyk-expensify · 2025-05-07T03:56:47Z

Desktop looks fine to me, but the mobile versions don't have a transparent scrim/overlay. You can't see the content behind the modal:

It should be slightly transparent like the rest of our modals and what we see on desktop 👍

nyomanjyotisa · 2025-05-07T10:34:56Z

The PR has been updated to address the native overlay issue. Here’s how it looks now:

iOS-Native.mp4

dannymcclain · 2025-05-07T12:46:18Z

Good shout Jon. Also, not sure how much we want to mess with this, but on mobile I would expect the overlay to fade in and the modal to slide up—that's how our other modal/bottom sheets work. (But I realize getting this perfect might not be our top priority.)

hungvu193 · 2025-05-07T14:18:40Z

So I think #58608 (comment) will look correctly

hungvu193 · 2025-05-08T09:27:48Z

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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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 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.ts 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.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
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: HybridApp

Android.mov

Android: mWeb Chrome

mAndroid.mov

iOS: HybridApp

fade.mov

push.from.bottom.mov

Screen.Recording.2025-05-08.at.16.26.52.mov

iOS: mWeb Safari

Safari.mov

MacOS: Chrome / Safari

Chrome.mov

MacOS: Desktop

Desktop.mov

blimpich

Looks good, nice work!

OSBotify · 2025-05-08T18:45:44Z

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

This reverts commit a957d55, reversing changes made to cefd53a.

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383"

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383" (cherry picked from commit 6569995) (cherry-picked to staging by francoisl)

kavimuru · 2025-05-15T13:45:33Z

Failing with original bug id #58383 on all the platforms

https://platform.applause.com/services/links/v1/external/8cb5866a057328d95dab393925d3e73b56b396fb99fd24257a68b777060e555b
https://platform.applause.com/services/links/v1/external/8c6097fe210443aabd768290f030417d258f78f16ff15a07004fc4bdc299f404
https://platform.applause.com/services/links/v1/external/e579d3801940074d4952d68244a2a32933c85d4b6e067d4761df5be28d6950f7
https://platform.utest.com/services/links/v1/internal/58344143?.mp4

hungvu193 · 2025-05-15T13:47:13Z

@kavimuru yes. This PR was reverted to fix few blockers

nyomanjyotisa added 2 commits March 18, 2025 10:13

Fix: On tapping device back button to close troubleshoot box from LHN…

b426a29

…, navigated out of site

ESLint fix

9b56f60

nyomanjyotisa marked this pull request as ready for review March 18, 2025 04:42

nyomanjyotisa requested a review from a team as a code owner March 18, 2025 04:42

melvin-bot bot requested a review from hungvu193 March 18, 2025 04:42

melvin-bot bot removed the request for review from a team March 18, 2025 04:42

nyomanjyotisa mentioned this pull request Mar 18, 2025

[Due for payment 2025-05-22] [$250][Back nav] LHN - On tapping device back button to close troubleshoot box from LHN, navigated out of site #58383

Open

8 tasks

Merge branch 'main' into issue-58383

dde4b86

prettier fix

aef18de

add modal screen

95b9e8f

nyomanjyotisa requested a review from a team as a code owner April 15, 2025 09:58

nyomanjyotisa added 3 commits April 15, 2025 18:00

Merge branch 'main' into issue-58383

5c02191

ESLint fix

b4d80e2

fix: allow modal to close on outside tap

bcece26

nyomanjyotisa added 2 commits April 15, 2025 20:32

fix: re-open search modal on forward button click

63f1bde

ESLint fix

1351266

hungvu193 reviewed May 5, 2025

View reviewed changes

nyomanjyotisa added 3 commits May 6, 2025 13:51

Merge branch 'main' into issue-58383

271f2db

native overlay

7585b32

prettier

4a14f09

hungvu193 reviewed May 7, 2025

View reviewed changes

native overlay

79a2b32

hungvu193 approved these changes May 8, 2025

View reviewed changes

melvin-bot bot requested a review from blimpich May 8, 2025 09:28

blimpich assigned nyomanjyotisa May 8, 2025

blimpich approved these changes May 8, 2025

View reviewed changes

blimpich merged commit a957d55 into Expensify:main May 8, 2025
17 checks passed

gijoe0295 mentioned this pull request May 13, 2025

[$250] WS Setting - Troubleshoot panel appears beneath the Edit Photo RHP #61949

Closed

8 tasks

francoisl added a commit that referenced this pull request May 13, 2025

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383"

f28fc60

This reverts commit a957d55, reversing changes made to cefd53a.

This was referenced May 13, 2025

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383" #61955

Merged

Chat Switching Broken - Always Returns to Same Chat #61928

Closed

luacmartins added a commit that referenced this pull request May 13, 2025

Merge pull request #61955 from Expensify/francois-revert-58608

6569995

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383"

OSBotify pushed a commit that referenced this pull request May 13, 2025

Merge pull request #61955 from Expensify/francois-revert-58608

5a9e3d4

Revert "Merge pull request #58608 from nyomanjyotisa/issue-58383" (cherry picked from commit 6569995) (cherry-picked to staging by francoisl)

mountiny mentioned this pull request May 14, 2025

Deploy Checklist: New Expensify 2025-05-13 #61917

Closed

github-actions bot mentioned this pull request May 16, 2025

Deploy Checklist: New Expensify 2025-05-15 #62161

Open

68 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: On tapping device back button to close troubleshoot box from LHN, navigated out of site #58608

Fix: On tapping device back button to close troubleshoot box from LHN, navigated out of site #58608

nyomanjyotisa commented Mar 18, 2025 •

edited

Loading

melvin-bot bot commented Mar 18, 2025

hungvu193 commented Mar 18, 2025 •

edited

Loading

hungvu193 commented Mar 19, 2025

nyomanjyotisa commented Mar 20, 2025

hungvu193 commented Mar 20, 2025

nyomanjyotisa commented Mar 21, 2025

hungvu193 commented Mar 28, 2025

hungvu193 commented Mar 29, 2025

nyomanjyotisa commented Apr 1, 2025

hungvu193 commented Apr 8, 2025

hungvu193 commented Apr 11, 2025

hungvu193 commented Apr 14, 2025

nyomanjyotisa commented Apr 15, 2025

hungvu193 commented Apr 15, 2025

nyomanjyotisa commented Apr 29, 2025

hungvu193 commented May 5, 2025

hungvu193 May 5, 2025

hungvu193 May 5, 2025

nyomanjyotisa May 6, 2025

hungvu193 May 7, 2025

hungvu193 commented May 7, 2025 •

edited

Loading

dubielzyk-expensify commented May 7, 2025

nyomanjyotisa commented May 7, 2025

dannymcclain commented May 7, 2025

hungvu193 commented May 7, 2025

hungvu193 commented May 8, 2025

blimpich left a comment

OSBotify commented May 8, 2025

kavimuru commented May 15, 2025

hungvu193 commented May 15, 2025

	animation: InternalPlatformAnimations.SLIDE_FROM_BOTTOM,
	animation: InternalPlatformAnimations.FADE,

Fix: On tapping device back button to close troubleshoot box from LHN, navigated out of site #58608

Fix: On tapping device back button to close troubleshoot box from LHN, navigated out of site #58608

Conversation

nyomanjyotisa commented Mar 18, 2025 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Mar 18, 2025

hungvu193 commented Mar 18, 2025 • edited Loading

hungvu193 commented Mar 19, 2025

nyomanjyotisa commented Mar 20, 2025

hungvu193 commented Mar 20, 2025

nyomanjyotisa commented Mar 21, 2025

hungvu193 commented Mar 28, 2025

hungvu193 commented Mar 29, 2025

nyomanjyotisa commented Apr 1, 2025

hungvu193 commented Apr 8, 2025

hungvu193 commented Apr 11, 2025

hungvu193 commented Apr 14, 2025

nyomanjyotisa commented Apr 15, 2025

hungvu193 commented Apr 15, 2025

nyomanjyotisa commented Apr 29, 2025

hungvu193 commented May 5, 2025

hungvu193 May 5, 2025

Choose a reason for hiding this comment

hungvu193 May 5, 2025

Choose a reason for hiding this comment

nyomanjyotisa May 6, 2025

Choose a reason for hiding this comment

hungvu193 May 7, 2025

Choose a reason for hiding this comment

hungvu193 commented May 7, 2025 • edited Loading

dubielzyk-expensify commented May 7, 2025

nyomanjyotisa commented May 7, 2025

dannymcclain commented May 7, 2025

hungvu193 commented May 7, 2025

hungvu193 commented May 8, 2025

Reviewer Checklist

Screenshots/Videos

blimpich left a comment

Choose a reason for hiding this comment

OSBotify commented May 8, 2025

kavimuru commented May 15, 2025

hungvu193 commented May 15, 2025

nyomanjyotisa commented Mar 18, 2025 •

edited

Loading

hungvu193 commented Mar 18, 2025 •

edited

Loading

hungvu193 commented May 7, 2025 •

edited

Loading