Navigate to expense detail page after adding a receipt by kubabutkiewicz · Pull Request #71818 · Expensify/App

kubabutkiewicz · 2025-10-03T15:34:51Z

Explanation of Change

Fixed Issues

$#70920
PROPOSAL:

Tests

Launch app as member
Open employee workspace chat
Create a manual expense
Open the expense
Tap plus icon and add a receipt
Verify user is redirected to expense details page.

Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

same as tests

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 verified there are no new alerts related to the canBeMissing param for useOnyx
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 new assets were added or existing ones were modified, I verified that:
- The assets are optimized and compressed (for SVG files, run npm run compress-svg)
- The assets load correctly across all supported platforms.
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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

… to inbox

melvin-bot · 2025-10-03T15:34:57Z

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

kubabutkiewicz · 2025-10-03T15:35:38Z

Hey @rafecolton I created a potential fix but I have some problem with building the app on my phone. Could you run the ad hoc builds so I could verify?

codecov · 2025-10-03T15:45:08Z

Codecov Report

❌ Patch coverage is 12.50000% with 28 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/libs/actions/App.ts	0.00%	13 Missing ⚠️
...u/request/step/IOURequestStepScan/index.native.tsx	0.00%	10 Missing ⚠️
src/libs/Navigation/NavigationRoot.tsx	44.44%	5 Missing ⚠️

Files with missing lines	Coverage Δ
src/CONST/index.ts	`85.84% <ø> (ø)`
src/libs/Navigation/NavigationRoot.tsx	`78.49% <44.44%> (-1.29%)`	⬇️
...u/request/step/IOURequestStepScan/index.native.tsx	`1.04% <0.00%> (-0.03%)`	⬇️
src/libs/actions/App.ts	`43.34% <0.00%> (-2.57%)`	⬇️

... and 21 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

rafecolton · 2025-10-03T22:21:45Z

Triggered the build

github-actions · 2025-10-03T22:22:10Z

🚧 @rafecolton has triggered a test Expensify/App build. You can view the workflow run here.

dukenv0307 · 2025-10-06T04:45:43Z

It doesn't work on my side @kubabutkiewicz

Screen.Recording.2025-10-06.at.11.42.42.mov

kubabutkiewicz · 2025-10-06T07:05:02Z

thanks for checking will be digging further

kubabutkiewicz · 2025-10-06T10:05:02Z

Hey @dukenv0307 is there is something I am doing wrong ?
For me its working 😅

ScreenRecording_10-06-2025.11-49-45_1.MP4

dukenv0307 · 2025-10-06T11:15:52Z

@kubabutkiewicz Can you please merge main? then I'll check again

dukenv0307 · 2025-10-06T11:25:37Z

@kubabutkiewicz Can you test on 1 transaction thread? It also works on my side when there are 2 transactions in the expense report, but it doesn't work on 1 transaction thread

…to fix-70920

kubabutkiewicz · 2025-10-07T15:20:38Z

I am still not able to reproduce that for me its working properly, I think, I am doing everything as described no?

ScreenRecording_10-07-2025.17-13-31_1.MP4

kubabutkiewicz · 2025-10-07T15:29:51Z

hmm maybe its android only , let me check that

kubabutkiewicz · 2025-10-08T08:21:47Z

Same on android, looking good 😅
https://github.com/user-attachments/assets/39c3c44b-fdb4-4b3f-afe4-09613c456624

dukenv0307 · 2025-10-09T02:27:18Z

@kubabutkiewicz After digging deeper, I found out that we can reproduce this issue by using the following steps:

Open App
Go to WS page
Select any WS
Go to WS chat
Select any expense
Click the receipt placeholder
Upload the receipt
Observe that after uploading the receipt, we'll navigate to LHN

Screen.Recording.2025-10-09.at.09.24.13.mov

dukenv0307 · 2025-10-09T02:29:36Z

@kubabutkiewicz The RCA is in

const reportsSplitNavigator = navigationState?.routes?.find((route) => route.name === 'ReportsSplitNavigator');
const hasLostNavigationsState = reportsSplitNavigator && !reportsSplitNavigator.state;

The first route ReportsSplitNavigator doesn't have the state, so we'll navigate to the home page

I think we should use findLast

kubabutkiewicz · 2025-10-09T15:08:08Z

@dukenv0307 I dont know whats going on but I am doing exactly same steps as you and stil working for me, I will just apply the fix you suggest and we can run new ad hoc build to check

ScreenRecording_10-09-2025.17-04-35_1.MP4

…ndLast for ReportsSplitNavigator

kubabutkiewicz · 2025-10-09T15:16:42Z

I pushed this change @dukenv0307. Could you @rafecolton run again the ad hoc builds 🙏

dukenv0307 · 2025-10-09T16:37:52Z

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

Screen.Recording.2025-10-09.at.23.26.23.mov

Android: mWeb Chrome

Screen.Recording.2025-10-09.at.23.33.25.mov

iOS: HybridApp

iOS: mWeb Safari

Screen.Recording.2025-10-09.at.23.34.14.mov

MacOS: Chrome / Safari

Screen.Recording.2025-10-09.at.23.35.24.mov

MacOS: Desktop

Screen.Recording.2025-10-09.at.23.42.27.mov

dukenv0307 · 2025-10-09T16:44:38Z

Thank you @kubabutkiewicz. This issue works well on my side. @mountiny @rafecolton Can you please trigger an ad-hoc build? We need to verify it on the real iOS device

github-actions · 2025-10-10T03:10:39Z

🚧 @rafecolton has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2025-10-10T14:04:27Z

HelpDot Documentation Review

Assessment Summary

After thorough analysis of PR #71818, this PR does not contain any HelpDot documentation changes. This is a code-only pull request that implements a navigation fix for expense receipt scanning functionality.

PR Analysis

PR Title: Navigate to expense detail page after adding a receipt
Author: @kubabutkiewicz
Files Changed: 5 TypeScript/JavaScript files only

Files Modified (Code Only)

src/CONST/index.ts - Updated exclude list for last visited path
src/libs/Navigation/NavigationRoot.tsx - Enhanced navigation logic
src/libs/actions/App.ts - Added navigation action for expense details
src/libs/shouldOpenLastVisitedPath/index.native.ts - Updated path logic
src/pages/iou/request/step/IOURequestStepScan/index.native.tsx - Added navigation trigger

Recommendation

This PR should not be reviewed using HelpDot documentation criteria as it contains no documentation changes. The changes are purely functional code improvements for the expense scanning user flow.

For future reference, HelpDot documentation reviews should only be requested for PRs that modify files in the docs/ directory or other markdown documentation files.

Next Steps

Please direct this PR to appropriate code reviewers rather than documentation reviewers, as it implements a navigation enhancement rather than documentation updates.

mountiny

Looks good to me, but I would love a review from navigation team before merging

rafecolton

LGTM

mountiny · 2025-10-13T20:19:02Z

Bumped @adamgrzybowski and @WojtekBoman for a review, I think they both were ooo

WojtekBoman · 2025-10-14T06:56:20Z

 AppState.addEventListener('change', (nextAppState) => {
    if (nextAppState.match(/inactive|background/) && appState === 'active') {
        Log.info('Flushing logs as app is going inactive', true, {}, true);
+        saveCurrentPathBeforeBackground();


Hey, I'd like to make sure about this part :)

Why do we need to save it here? Can't we save it when we open this page like it's done in parseAndLogRoute?

Its added because we are trying to fix the issue when you are going to change some permissions in the OS settings then app navigation state is reset and user is navigated to Inbox. this is for saving the navigation state before doing that to be able then to navigate to the screen which user was before.

OK, I understand that part. I'm just wondering if we can save this information earlier. Now, saveCurrentPathBeforeBackground will be called every time the app goes to the background. Is the navigation state different when we go to the background and when we're on the scanned receipt screen?

I see CONST.EXCLUDE_FROM_LAST_VISITED_PATH has been modified, so updateLastVisitedPath won't be called in parseAndLogRoute when we're on this page

…ndex now

…to fix-70920

mountiny

@dukenv0307 could you retest now after the changes too please?

dukenv0307 · 2025-10-16T04:54:23Z

Screen.Recording.2025-10-16.at.11.53.02.mov

dukenv0307 · 2025-10-16T04:54:48Z

LGTM

…l/Expensify-App into fix-70920

kubabutkiewicz · 2025-10-20T09:57:57Z

@mountiny could you take a look here?

kubabutkiewicz · 2025-10-22T09:08:26Z

@mountiny @rafecolton Can we merge this PR 😄 ?

mountiny

Ok I will go ahead and merge to avoid more conflicts

OSBotify · 2025-10-23T13:09:05Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.37-1 🚀

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

OSBotify · 2025-10-24T17:51:16Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

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

recreated a previous Pr and attempt to fix the issue with redirecting…

773b3aa

… to inbox

kubabutkiewicz requested a review from a team as a code owner October 3, 2025 15:34

melvin-bot Bot assigned kubabutkiewicz Oct 3, 2025

melvin-bot Bot requested review from dukenv0307 and removed request for a team October 3, 2025 15:34

This comment has been minimized.

Sign in to view

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

841c415

…to fix-70920

fix: update navigation state handling in IOURequestStepScan to use fi…

2d6c9e2

…ndLast for ReportsSplitNavigator

dukenv0307 approved these changes Oct 9, 2025

View reviewed changes

melvin-bot Bot requested a review from mountiny October 9, 2025 16:43

mountiny reviewed Oct 10, 2025

View reviewed changes

mountiny requested review from WojtekBoman and adamgrzybowski October 10, 2025 14:30

rafecolton previously approved these changes Oct 10, 2025

View reviewed changes

WojtekBoman reviewed Oct 14, 2025

View reviewed changes

Comment thread src/libs/shouldOpenLastVisitedPath/index.native.ts

remove native file for shouldOpenLastVisitedPath as its the same as i…

98ce645

…ndex now

kubabutkiewicz dismissed rafecolton’s stale review via 98ce645 October 14, 2025 10:36

adamgrzybowski approved these changes Oct 15, 2025

View reviewed changes

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

fe2f940

…to fix-70920

mountiny approved these changes Oct 15, 2025

View reviewed changes

dukenv0307 approved these changes Oct 16, 2025

View reviewed changes

melvin-bot Bot requested a review from mountiny October 16, 2025 04:54

Merge branches 'main' and 'fix-70920' of github.com:callstack-interna…

11249bb

…l/Expensify-App into fix-70920

mountiny approved these changes Oct 22, 2025

View reviewed changes

mountiny merged commit ba8e4c8 into Expensify:main Oct 22, 2025
24 checks passed

github-actions Bot mentioned this pull request Oct 22, 2025

Investigate workflow job failing on main: test / test (job 1) #73209

Closed

OSBotify mentioned this pull request Oct 23, 2025

Deploy Checklist: New Expensify 2025-10-23 #73307

Closed

88 tasks

aldo-expensify mentioned this pull request Oct 23, 2025

Revert "Navigate to expense detail page after adding a receipt" #73353

Closed

melvin-bot Bot mentioned this pull request Oct 24, 2025

[Due for payment 2025-10-31] [$50] Expense - After adding receipt in employee workspace directed to inbox #70920

Closed

8 tasks

dukenv0307 mentioned this pull request Nov 4, 2025

[$250] Scan - User is dropped in the Inbox after enabling camera permission and replacing receipt #65992

Closed

8 tasks

Conversation

kubabutkiewicz commented Oct 3, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Oct 3, 2025

Uh oh!

kubabutkiewicz commented Oct 3, 2025

Uh oh!

codecov Bot commented Oct 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

rafecolton commented Oct 3, 2025

Uh oh!

github-actions Bot commented Oct 3, 2025

Uh oh!

This comment has been minimized.

dukenv0307 commented Oct 6, 2025

Uh oh!

kubabutkiewicz commented Oct 6, 2025

Uh oh!

kubabutkiewicz commented Oct 6, 2025

Uh oh!

dukenv0307 commented Oct 6, 2025

Uh oh!

dukenv0307 commented Oct 6, 2025

Uh oh!

kubabutkiewicz commented Oct 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kubabutkiewicz commented Oct 7, 2025

Uh oh!

kubabutkiewicz commented Oct 8, 2025

Uh oh!

dukenv0307 commented Oct 9, 2025

Uh oh!

dukenv0307 commented Oct 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kubabutkiewicz commented Oct 9, 2025

Uh oh!

kubabutkiewicz commented Oct 9, 2025

Uh oh!

dukenv0307 commented Oct 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

dukenv0307 commented Oct 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Oct 10, 2025

Uh oh!

github-actions Bot commented Oct 10, 2025

HelpDot Documentation Review

Assessment Summary

PR Analysis

Files Modified (Code Only)

Recommendation

Next Steps

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

rafecolton left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny commented Oct 13, 2025

Uh oh!

WojtekBoman Oct 14, 2025

Choose a reason for hiding this comment

Uh oh!

kubabutkiewicz Oct 14, 2025

Choose a reason for hiding this comment

codecov Bot commented Oct 3, 2025 •

edited

Loading

kubabutkiewicz commented Oct 7, 2025 •

edited

Loading

dukenv0307 commented Oct 9, 2025 •

edited

Loading

dukenv0307 commented Oct 9, 2025 •

edited

Loading

dukenv0307 commented Oct 9, 2025 •

edited

Loading