refactor: Remove shouldHandleNavigation from sendMoney and submitPerDiemExpense by TaduJR · Pull Request #86619 · Expensify/App

TaduJR · 2026-03-29T07:33:36Z

Explanation of Change

Creates two new navigation utilities in src/libs/Navigation/helpers/ as the second step of #84631, and wires them up with initial callers to prove they work.

navigateAfterExpenseCreate: handles post-creation navigation - either dismisses modal and opens the report, or navigates to the Search page (Expenses/Invoices) when created from the FAB.
dismissModalAndOpenReportInInboxTab: handles modal dismissal across multiple layout contexts (super-wide RHP, wide RHP, search page, default).

Callers wired up:

sendMoneyElsewhere / sendMoneyWithWallet: navigation moved from SendMoney.ts to IOURequestStepConfirmation.tsx and IOURequestStepAmount.tsx. Functions refactored from positional params to SendMoneyActionParams object. UI pre-computes the chat report ID via resolveOptimisticChatReportID and passes optimisticChatReportID to the action so both sides agree on the report identity.
submitPerDiemExpense: removed shouldHandleNavigation parameter. Navigation moved from PerDiem.ts to IOURequestStepConfirmation.tsx using navigateAfterExpenseCreate. Action accepts optimisticChatReportID. UI assembles all navigation data locally.

Fixed Issues

$ #84631
PROPOSAL: #84631 (comment)

Tests

Prerequisites

Two accounts: Test User A (you) and Test User B (recipient)
Test User A has an Expensify Wallet set up (for "Pay with wallet" tests)
A workspace with Per Diem enabled and rates configured

Send Money - From a Chat

1. Mark as paid from a DM chat

Open the DM chat with Test User B
Tap the + button in the chat
Select Pay
Enter an amount (e.g. $5.00) and tap Next
On the confirmation page, tap Mark as paid
Verify: Modal dismisses and the DM chat with Test User B is displayed
Verify: A payment preview card is visible in the chat

2. Pay with wallet from a DM chat

Open the DM chat with Test User B
Tap the + button in the chat
Select Pay
Enter an amount (e.g. $3.00) and tap Next
On the confirmation page, tap Pay with wallet
Verify: Modal dismisses and the DM chat with Test User B is displayed
Verify: A payment preview card is visible in the chat

Send Money - From Global Create

3. Mark as paid from the global + button

Go to the Inbox tab (not inside any specific chat)
Tap the global + button
Start a send money flow and select Test User B as the recipient
Enter an amount and tap Next
On the confirmation page, tap Mark as paid
Verify: Modal dismisses and the DM chat with Test User B opens showing the payment

4. Pay with wallet from the global + button

Go to the Inbox tab
Tap the global + button
Start a send money flow, select Test User B
Enter an amount and tap Next
On the confirmation page, tap Pay with wallet
Verify: Modal dismisses and the DM chat with Test User B opens showing the payment

Send Money - Quick Action (Skip Confirmation)

5. Send money via quick action

Ensure a quick action for "Pay Someone" is set with Test User B
From the Inbox tab, tap the + button
The quick action "Pay [Test User B]" should be visible -- tap it
Enter an amount (e.g. $2.00) and tap Send
Verify: Payment is created without showing a confirmation page
Verify: Modal dismisses and the DM chat with Test User B opens showing the payment

Submit Per Diem Expense

6. Submit per diem from the Inbox tab

Go to the Inbox tab
Tap the + button
Select Create expense > Per Diem tab
Select a workspace (if multiple per-diem workspaces exist)
Select a destination/rate
Enter subrate quantities and date range
Tap Confirm
Verify: Modal dismisses and the workspace chat opens showing the per diem expense
Verify: The expense appears with correct per diem details

7. Submit per diem from the Search tab

Go to the Search tab (not the Inbox)
Tap the + button
Select Create expense > Per Diem tab
Complete the per diem flow (workspace, destination, subrates, dates)
Tap Confirm
Verify: Modal dismisses and the Search Expenses page is displayed
Verify: The newly created per diem expense is visible in the search results

8. Submit per diem from within a workspace chat

Open a workspace policy expense chat
Tap the + button inside the chat
Select Create expense > Per Diem tab
Complete the per diem flow
Tap Confirm
Verify: Modal dismisses and returns to the workspace chat
Verify: The per diem expense preview is visible in the chat

9. Submit per diem from an existing expense report

Open an existing expense report for a workspace
Start a new per diem expense from within the report
Complete the per diem flow
Tap Confirm
Verify: Modal dismisses and the expense report is displayed with the new per diem added

10. Track per diem for yourself

Tap the + button
Start a per diem as a personal track (self-DM)
Complete the per diem flow
Tap Confirm
Verify: Modal dismisses and your self-DM opens showing the tracked per diem

Per Diem - New Chat

11. Submit per diem to a workspace you haven't used before

On a workspace where you haven't submitted expenses before (no existing chat)
Submit a per diem expense via the + button
Complete the full per diem flow
Verify: A new workspace chat is created and the modal dismisses to it correctly
Verify: The per diem expense is visible in the newly created chat

Verify that no errors appear in the JS console

Offline tests

Same as 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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Mac-Chrome.mp4

…tInInboxTab navigation helpers

melvin-bot · 2026-03-29T07:33:43Z

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

codecov · 2026-03-29T07:40:27Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/libs/IOUUtils.ts	`73.46% <100.00%> (+0.69%)`	⬆️
src/libs/actions/IOU/PerDiem.ts	`70.63% <100.00%> (-0.38%)`	⬇️
src/libs/actions/IOU/SendMoney.ts	`0.00% <0.00%> (ø)`
...rc/pages/iou/request/step/IOURequestStepAmount.tsx	`65.34% <0.00%> (ø)`
...s/Navigation/helpers/navigateAfterExpenseCreate.ts	`87.09% <87.09%> (ø)`
...es/iou/request/step/IOURequestStepConfirmation.tsx	`55.87% <4.54%> (-1.70%)`	⬇️
...ion/helpers/dismissModalAndOpenReportInInboxTab.ts	`27.90% <27.90%> (ø)`
... and 7 files with indirect coverage changes

linhvovan29546 · 2026-03-29T07:48:42Z

No callers are wired up in this PR - that happens in subsequent PRs.

@TaduJR Can we add at least one caller here to ensure the function works as expected?

TaduJR · 2026-03-29T08:08:11Z

@linhvovan29546

Sure thing, we could but that is going to be started on step 3 from the proposal currently the step 2 says this

Step 2: Create a navigation utility in the Navigation helpers layer
Extract the navigation logic from dismissModalAndOpenReportInInboxTab and the navigation portion of handleNavigateAfterExpenseCreate into a utility in src/libs/Navigation/helpers/. This is a plain function (not a hook) so it avoids hook rules constraints and can be called from callbacks, loops, or conditional branches within view-layer code. Important constraint: this utility must only be invoked from view-layer entrypoints (components and hooks), never from src/libs/actions/ or action-adjacent files, otherwise we recreate the same violation this issue is fixing.
App

But if you insist we can do that.

BTW I was thinking to create an ESLint rule to not introduce this again WDYT?

Important constraint: this utility must only be invoked from view-layer entrypoints (components and hooks), never from src/libs/actions/ or action-adjacent files, otherwise we recreate the same violation this issue is fixing.

linhvovan29546 · 2026-03-29T08:16:38Z

Sure thing, we could but that is going to be started on step 3 from the proposal currently the step 2 says this

Please add at least one caller to ensure the function works as expected. This is part of the plan and can be adjusted when we open the PR

BTW I was thinking to create an ESLint rule to not introduce this again WDYT?

We can add the ESLint rule, but let’s discuss it after the final PR

…nInboxTab navigation helper

TaduJR · 2026-03-29T10:55:49Z

@linhvovan29546

Added sendMoneyElsewhere and sendMoneyWithWallet as callers both UI callsites (IOURequestStepConfirmation.tsx and IOURequestStepAmount.tsx) now use the new dismissModalAndOpenReportInInboxTab helper directly.

For navigateAfterExpenseCreate, wiring up a caller requires removing shouldHandleNavigation from an action function, which is PR 3's scope. Since navigateAfterExpenseCreate internally delegates to dismissModalAndOpenReportInInboxTab, the lower-level utility is already exercised through the sendMoney wiring.

WDYT about navigateAfterExpenseCreate?

linhvovan29546 · 2026-03-29T11:02:11Z

@TaduJR I think we can remove shouldHandleNavigation, right?

TaduJR · 2026-03-29T11:17:52Z

@linhvovan29546

Yes, we can remove shouldHandleNavigation from one function (e.g. submitPerDiemExpense) in this PR to prove navigateAfterExpenseCreate works end-to-end.

linhvovan29546 · 2026-03-30T15:16:15Z

Yes, we can remove shouldHandleNavigation from one function (e.g. submitPerDiemExpense) in this PR to prove navigateAfterExpenseCreate works end-to-end.

Ok, please remove shouldHandleNavigation

joekaufmanexpensify · 2026-03-30T21:32:22Z

No product review needed

…de-to-keep-navigation-handling-in-the-UI-components

… wire up navigateAfterExpenseCreate

…de-to-keep-navigation-handling-in-the-UI-components

linhvovan29546 · 2026-03-31T14:52:38Z

@TaduJR Please take a look at this comment #84631 (comment). We should not return the payload from the function.

TaduJR · 2026-04-02T05:57:12Z

@TaduJR Please take a look at this comment #84631 (comment). We should not return the payload from the function.

Yea, I was testing the new utility function before proceeding.

… report IDs in UI callers

…y return

…ution

…ReportID

…de-to-keep-navigation-handling-in-the-UI-components

TaduJR · 2026-04-07T10:14:13Z

@codex review

chatgpt-codex-connector · 2026-04-07T10:28:15Z

Codex Review: Didn't find any major issues. You're on a roll.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…de-to-keep-navigation-handling-in-the-UI-components # Conflicts: # src/libs/IOUUtils.ts

…Transactions with useReportTransactions hook

linhvovan29546 · 2026-04-13T07:44:14Z

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
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 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

N/A—the change should work on all platforms.

Android: mWeb Chrome

N/A—the change should work on all platforms.

iOS: HybridApp

Screen.Recording.2026-04-13.at.17.03.18.mov

Screen.Recording.2026-04-13.at.17.02.30.mov

iOS: mWeb Safari

N/A—the change should work on all platforms.

MacOS: Chrome / Safari

Screen.Recording.2026-04-13.at.16.55.27.mov

Screen.Recording.2026-04-13.at.15.22.45.mov

Screen.Recording.2026-04-13.at.15.19.21.mov

Screen.Recording.2026-04-13.at.15.17.50.mov

Screen.Recording.2026-04-13.at.15.05.54.mov

linhvovan29546 · 2026-04-13T07:44:32Z

@TaduJR Conflict again!

linhvovan29546 · 2026-04-13T08:26:25Z

Bug: I don’t see the per diem after creating it. I can only reproduce this on this PR

Screen.Recording.2026-04-13.at.15.20.04.mov

linhvovan29546 · 2026-04-13T08:26:43Z

Could you please merge main and resolve the conflicts so I can test again?

…de-to-keep-navigation-handling-in-the-UI-components

…de-to-keep-navigation-handling-in-the-UI-components # Conflicts: # src/pages/iou/request/step/IOURequestStepConfirmation.tsx

TaduJR · 2026-04-13T09:36:28Z

@linhvovan29546

Could you please merge main and resolve the conflicts so I can test again?

Merged with latest main.

Bug: I don’t see the per diem after creating it. I can only reproduce this on this PR

Unable to reproduce on the latest merged main.

Mac-Chrome.mp4

github-actions · 2026-04-13T13:01:58Z

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

github-actions · 2026-04-13T13:06:43Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #86619.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-e3d8b78-08ff3fc-04451a178139ff3470d2e24b3c6115cdb2a6aebe/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-e3d8b78-08ff3fc-7d1a95eb7751d7cae4988e2d4baeac7a1bbd45f3/index.html

Web 🕸️
https://86619.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-13T13:10:06Z

✋ 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 · 2026-04-13T20:32:35Z

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.59-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

Bundle Size Analysis (Sentry):

Android

MelvinBot · 2026-04-13T20:33:56Z

No help site changes are required for this PR.

This is a purely internal code refactoring that moves navigation handling from action files (SendMoney.ts, PerDiem.ts) into UI components and creates new navigation utility functions (navigateAfterExpenseCreate, dismissModalAndOpenReportInInboxTab). There are no user-facing changes — no new features, no renamed UI elements, no changed user flows, and no modified settings or labels.

OSBotify · 2026-04-16T03:29:14Z

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.3.59-4 🚀

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

refactor: Add navigateAfterExpenseCreate and dismissModalAndOpenRepor…

a0da86a

…tInInboxTab navigation helpers

TaduJR requested review from a team as code owners March 29, 2026 07:33

melvin-bot Bot assigned TaduJR Mar 29, 2026

melvin-bot Bot requested review from joekaufmanexpensify and linhvovan29546 and removed request for a team March 29, 2026 07:33

melvin-bot Bot removed the request for review from a team March 29, 2026 07:33

refactor: Wire up sendMoney callers to use dismissModalAndOpenReportI…

e1cc99a

…nInboxTab navigation helper

TaduJR changed the title ~~[No-QA] refactor: Add post-expense-creation navigation helpers~~ refactor: Add post-expense-creation navigation helpers Mar 29, 2026

joekaufmanexpensify removed their request for review March 30, 2026 21:32

TaduJR added 3 commits March 31, 2026 13:11

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

03099eb

…de-to-keep-navigation-handling-in-the-UI-components

refactor: Remove shouldHandleNavigation from submitPerDiemExpense and…

e66ff45

… wire up navigateAfterExpenseCreate

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

8c9bf99

…de-to-keep-navigation-handling-in-the-UI-components

TaduJR marked this pull request as draft April 2, 2026 07:15

TaduJR added 3 commits April 2, 2026 11:53

refactor: sendMoney to params object and pre-generate optimistic chat…

d700b5e

… report IDs in UI callers

fix: per-diem policy expense chat lookup and guard navigation on earl…

2b58745

…y return

fix: Add getChatByParticipants fallback for expense report chat resol…

c86cc79

…ution

TaduJR added 2 commits April 6, 2026 09:54

test: Add unit tests for navigation helpers and resolveOptimisticChat…

143a765

…ReportID

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

80708af

…de-to-keep-navigation-handling-in-the-UI-components

chore: CI restart

f4d4f40

linhvovan29546 suggested changes Apr 8, 2026

View reviewed changes

Comment thread src/libs/Navigation/helpers/navigateAfterExpenseCreate.ts

Comment thread src/pages/iou/request/step/IOURequestStepAmount.tsx Outdated

TaduJR added 2 commits April 9, 2026 12:06

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

2b7d7d3

…de-to-keep-navigation-handling-in-the-UI-components # Conflicts: # src/libs/IOUUtils.ts

fix: Restore sync-first navigation optimization and replace getReport…

8a07284

…Transactions with useReportTransactions hook

TaduJR added 2 commits April 13, 2026 12:01

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

f83047e

…de-to-keep-navigation-handling-in-the-UI-components

Merge branch 'main' of https://github.com/TaduJR/App into refactor-co…

0d3f409

…de-to-keep-navigation-handling-in-the-UI-components # Conflicts: # src/pages/iou/request/step/IOURequestStepConfirmation.tsx

linhvovan29546 approved these changes Apr 13, 2026

View reviewed changes

melvin-bot Bot requested a review from Valforte April 13, 2026 10:07

Valforte approved these changes Apr 13, 2026

View reviewed changes

Valforte merged commit e3d8b78 into Expensify:main Apr 13, 2026
32 checks passed

OSBotify mentioned this pull request Apr 13, 2026

Deploy Checklist: New Expensify 2026-04-13 #87792

Closed

89 tasks

This was referenced Apr 14, 2026

[$250] IOU - Missing Mark as Paid or Pay with Wallet option when sending Money request #87841

Closed

[Exploratory] Hybrid - Per Diem - Not here page briefly appear when create Per Diem in SelfDM #87882

Closed

melvin-bot Bot mentioned this pull request Apr 16, 2026

[Due for payment 2026-07-16] [$250] Refactor code to keep navigation handling in the UI components #84631

Open

TaduJR mentioned this pull request Apr 16, 2026

refactor: Remove shouldHandleNavigation from requestMoney and trackExpense #88055

Merged

54 tasks

Uh oh!

Conversation

TaduJR commented Mar 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Prerequisites

Send Money - From a Chat

Send Money - From Global Create

Send Money - Quick Action (Skip Confirmation)

Submit Per Diem Expense

Per Diem - New Chat

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Mar 29, 2026

Uh oh!

codecov Bot commented Mar 29, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

linhvovan29546 commented Mar 29, 2026

Uh oh!

TaduJR commented Mar 29, 2026

Uh oh!

linhvovan29546 commented Mar 29, 2026

Uh oh!

TaduJR commented Mar 29, 2026

Uh oh!

linhvovan29546 commented Mar 29, 2026

Uh oh!

TaduJR commented Mar 29, 2026

Uh oh!

linhvovan29546 commented Mar 30, 2026

Uh oh!

joekaufmanexpensify commented Mar 30, 2026

Uh oh!

linhvovan29546 commented Mar 31, 2026

Uh oh!

TaduJR commented Apr 2, 2026

Uh oh!

TaduJR commented Apr 7, 2026

Uh oh!

chatgpt-codex-connector Bot commented Apr 7, 2026

Uh oh!

Uh oh!

Uh oh!

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

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

linhvovan29546 commented Apr 13, 2026

Uh oh!

linhvovan29546 commented Apr 13, 2026

Uh oh!

linhvovan29546 commented Apr 13, 2026

Uh oh!

TaduJR commented Apr 13, 2026

Uh oh!

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

github-actions Bot commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 13, 2026

Uh oh!

MelvinBot commented Apr 13, 2026

Uh oh!

OSBotify commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

TaduJR commented Mar 29, 2026 •

edited

Loading

codecov Bot commented Mar 29, 2026 •

edited by github-actions Bot

Loading

linhvovan29546 commented Apr 13, 2026 •

edited

Loading