update empty receipt in wide RHP to allow picking the receipt by nkdengineer · Pull Request #81467 · Expensify/App

nkdengineer · 2026-02-05T03:54:45Z

Explanation of Change

update empty receipt in wide RHP to allow picking the receipt

Fixed Issues

$ #79189
PROPOSAL:

Tests (Web only)

Create an expense without a receipt
Open the wide RHP report
Click on the empty receipt area
Verify that the file picker is opened
Select a valid receipt
Verify that the receipt is added to the transaction

Verify that no errors appear in the JS console

Offline tests

Same

QA Steps

Same as test

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

Screen.Recording.2026-02-05.at.10.50.38.mov

iOS: Native

Screen.Recording.2026-02-05.at.10.48.19.mov

iOS: mWeb Safari

Screen.Recording.2026-02-05.at.10.49.48.mov

MacOS: Chrome / Safari

Screen.Recording.2026-02-05.at.10.46.57.mov

codecov · 2026-02-05T04:06:18Z

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/components/ReceiptEmptyState.tsx	`100.00% <100.00%> (ø)`
src/styles/index.ts	`45.87% <ø> (ø)`
...nents/ReportActionItem/MoneyRequestReceiptView.tsx	`56.36% <33.33%> (+54.49%)`	⬆️
src/components/DropZone/DualDropZone.tsx	`70.58% <63.63%> (-4.42%)`	⬇️
... and 36 files with indirect coverage changes

melvin-bot · 2026-02-06T02:01:55Z

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

src/components/ReceiptEmptyState.tsx

src/components/ReportActionItem/MoneyRequestReceiptView.tsx

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8f9724dfee

ℹ️ 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".

src/components/ReceiptEmptyState.tsx

DylanDylann · 2026-02-09T08:25:42Z

@nkdengineer Could you check all the above comments from codex, gh action and codecov?

trjExpensify

LGTM! CC: @Expensify/design

dannymcclain · 2026-02-09T14:35:24Z

Running a build to test it out!

github-actions · 2026-02-09T14:36:16Z

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

dannymcclain · 2026-02-09T15:21:41Z

Looking pretty good - the only slightly weird thing here is that you get this kinda awkward drop zone:

CleanShot.2026-02-09.at.09.18.43.mp4

It totally works, it just feels ever so slightly odd that receipt empty state says "or drag and drop one here" but then you get a totally different drop zone when dragging. Not sure if we need to do anything about it, but wanted to call it out. cc @Expensify/design

nkdengineer · 2026-02-09T16:14:11Z

@DylanDylann Checked all of them

dubielzyk-expensify · 2026-02-10T00:07:24Z

It totally works, it just feels ever so slightly odd that receipt empty state says "or drag and drop one here" but then you get a totally different drop zone when dragging. Not sure if we need to do anything about it, but wanted to call it out. cc @Expensify/design

Yeah I totally agree. It kinda feels like we now have a good separation of receipt and fields so I wonder if we should just have it be split horizontally so that dropping on the receipt thumbnail adds as receipt, but dropping it on the right fields or comments adds it to the thread. Kinda feels logical to me anyways? Then on smaller viewports, we could revert to the top/below treatment

DylanDylann · 2026-02-10T07:06:32Z

IMO, we shouldn't have a horizontal split on the empty receipt view. This view is only meant to notify users that the receipt is empty and that they can drag a receipt into it. I don't think we need to display anything additional to indicate that users can drag an attachment into the chat.

DylanDylann · 2026-02-10T07:06:45Z

@nkdengineer We have a lint warning

shawnborton · 2026-02-10T07:18:52Z

Hmm I'm not entirely sure, I could see both sides of that but I think if we want to be consistent, we should allow the split drop zones since users can add any attachments they want to the expense chat. So I personally would vote to try the vertical 50/50 split if we can.

DylanDylann · 2026-02-10T07:29:08Z

src/components/ReceiptEmptyState.tsx

    const theme = useTheme();
    const isLoadedRef = useRef(false);
    const icons = useMemoizedLazyExpensifyIcons(['ReceiptPlaceholderPlus', 'Receipt']);
+    const {validateFiles, PDFValidationComponent, ErrorModal} = useFilesValidation(onReplaceReceipt);


@nkdengineer I'm curious why we're using onReplaceReceipt here? Shouldn't this change only affect the add new receipt flow?

Add/Update the receipt, we use the same function is replaceReceipt function

I agree, but I'd prefer sticking with setReceiptFiles to keep the meaning clear, just like we did in the original implementation.

@DylanDylann I updated.

DylanDylann · 2026-02-10T07:35:05Z

@nkdengineer ReceiptEmptyState is used in other places. Should we limit this change to avoid impacting those places?

DylanDylann · 2026-02-24T04:32:17Z

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

@nkdengineer Please notice the codecov's comment

DylanDylann · 2026-02-24T04:32:41Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b9543f6431

ℹ️ 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".

chatgpt-codex-connector · 2026-02-24T04:45:48Z

src/components/ReportActionItem/MoneyRequestReceiptView.tsx

+        const source = URL.createObjectURL(file as Blob);
+        replaceReceipt({transactionID: linkedTransactionID, file: file as File, source, transactionPolicy: policy, transactionPolicyCategories: policyCategories});


Use file URI when replacing receipt from wide RHP

setReceiptFile now always derives source via URL.createObjectURL(file as Blob), but the wide-RHP picker can run through AttachmentPicker/index.native.tsx, which returns native FileObjects with a uri rather than a web Blob/File; the existing native scan flow already uses file.uri directly (IOURequestStepScan/index.native.tsx). In native large-screen contexts where isDisplayedInWideRHP is true, this path can throw or produce an invalid source, preventing replaceReceipt from attaching the selected receipt.

Useful? React with 👍 / 👎.

It's incorrect, the wide-RHP is only available on web.

nkdengineer · 2026-02-24T04:55:34Z

@nkdengineer Please notice the codecov's comment

@DylanDylann It's decreased because we've changed these files, and we don't have any automation tests. But how can we write the test with the flow open picker/drag and drop? Let me know if I missed something.

src/components/DropZone/DualDropZone.tsx

DylanDylann · 2026-02-24T05:09:50Z

It's decreased because we've changed these files, and we don't have any automation tests

If that's the case, I think the test coverage should be maintained instead of decreasing. Perhaps these components are used in other components that already have test coverage.

nkdengineer · 2026-02-24T05:15:30Z

If that's the case, I think the test coverage should be maintained instead of decreasing

So what is the decrease here? Is this the manual test that isn't covered?

src/components/DropZone/DualDropZone.tsx

DylanDylann · 2026-02-24T05:22:43Z

So what is the decrease here? Is this the manual test that isn't covered?

These are unit tests

DylanDylann · 2026-02-24T05:53:33Z

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.2026-02-26.at.12.28.50.mov

Android: mWeb Chrome

Screen.Recording.2026-02-26.at.12.26.51.mov

iOS: HybridApp

iOS: mWeb Safari

Screen.Recording.2026-02-26.at.12.28.14.mov

MacOS: Chrome / Safari

Screen.Recording.2026-02-26.at.12.17.32.mov

nkdengineer · 2026-02-24T05:59:39Z

These are unit tests

As I mentioned above, we don't have a way to write the test with the flow open picker/drag and drop.

DylanDylann · 2026-02-24T06:11:56Z

As I mentioned above, we don't have a way to write the test with the flow open picker/drag and drop.

Could you clarify what's blocking here? This is draft tests, I think it can resolve our problem here

DualDropZoneTest.tsx
MoneyRequestReceiptViewTest.tsx
ReceiptEmptyStateTest.tsx

nkdengineer · 2026-02-25T10:21:06Z

@DylanDylann Updated the test. For DualDropZone, can't add the test since the platform in the test is the native platform and DragAndDropConsumer renders nothing in native.

DylanDylann

LGTM

github-actions · 2026-02-27T20:56:32Z

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

github-actions · 2026-02-27T21:01:11Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-467f1c9-7ab88ad-73660a876eb9e736bcb51e8cd950b81891ee8841/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-467f1c9-7ab88ad-532b33f98d9195d4d66b2597f1153dca0075940e/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-02T12:09:42Z

✋ 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-03-02T23:01:29Z

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.3.28-0 🚀

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

OSBotify · 2026-03-04T03:16:17Z

🚀 Deployed to staging by https://github.com/NikkiWines in version: 9.3.30-0 🚀

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

OSBotify · 2026-03-04T18:06:38Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.30-3 🚀

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

update empty receipt in wide RHP to allow picking the receipt

8f9724d

melvin-bot bot assigned nkdengineer Feb 5, 2026

nkdengineer mentioned this pull request Feb 5, 2026

[Due for payment 2026-03-11] [CFI] Update empty receipt section in the expense RHP #79189

Closed

nkdengineer marked this pull request as ready for review February 6, 2026 02:01

nkdengineer requested review from a team as code owners February 6, 2026 02:01

melvin-bot bot requested review from DylanDylann and trjExpensify February 6, 2026 02:01

melvin-bot bot removed request for a team February 6, 2026 02:01

github-actions bot reviewed Feb 6, 2026

View reviewed changes

src/components/ReceiptEmptyState.tsx Show resolved Hide resolved

github-actions bot reviewed Feb 6, 2026

View reviewed changes

src/components/ReportActionItem/MoneyRequestReceiptView.tsx Show resolved Hide resolved

github-actions bot reviewed Feb 6, 2026

View reviewed changes

src/components/ReportActionItem/MoneyRequestReceiptView.tsx Show resolved Hide resolved

chatgpt-codex-connector bot reviewed Feb 6, 2026

View reviewed changes

src/components/ReceiptEmptyState.tsx Show resolved Hide resolved

trjExpensify previously approved these changes Feb 9, 2026

View reviewed changes

This comment has been minimized.

Sign in to view

Merge branch 'main' into fix/79189-1

06c93af

DylanDylann reviewed Feb 10, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Feb 24, 2026

View reviewed changes

DylanDylann reviewed Feb 24, 2026

View reviewed changes

src/components/DropZone/DualDropZone.tsx Outdated Show resolved Hide resolved

nkdengineer added 2 commits February 24, 2026 12:11

Merge branch 'main' into fix/79189-1

33098d1

remove super wide RHP case

7944cb4

DylanDylann reviewed Feb 24, 2026

View reviewed changes

src/components/DropZone/DualDropZone.tsx Show resolved Hide resolved

nkdengineer added 2 commits February 25, 2026 16:50

Merge branch 'main' into fix/79189-1

e5f0f51

add test

3480b22

Merge branch 'main' into fix/79189-1

ed5cb10

DylanDylann approved these changes Feb 26, 2026

View reviewed changes

melvin-bot bot requested a review from NikkiWines February 26, 2026 05:30

NikkiWines approved these changes Feb 27, 2026

View reviewed changes

NikkiWines merged commit 467f1c9 into Expensify:main Feb 27, 2026
30 checks passed

github-actions bot mentioned this pull request Feb 27, 2026

Investigate workflow job failing on main: test / test (job 8) #83757

Closed

OSBotify mentioned this pull request Mar 2, 2026

Deploy Checklist: New Expensify 2026-03-02 #83947

Closed

		const source = URL.createObjectURL(file as Blob);
		replaceReceipt({transactionID: linkedTransactionID, file: file as File, source, transactionPolicy: policy, transactionPolicyCategories: policyCategories});

Conversation

nkdengineer commented Feb 5, 2026

Explanation of Change

Fixed Issues

Tests (Web only)

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Feb 5, 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!

melvin-bot bot commented Feb 6, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

DylanDylann commented Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

dannymcclain commented Feb 9, 2026

Uh oh!

github-actions bot commented Feb 9, 2026

Uh oh!

This comment has been minimized.

dannymcclain commented Feb 9, 2026

Uh oh!

nkdengineer commented Feb 9, 2026

Uh oh!

dubielzyk-expensify commented Feb 10, 2026

Uh oh!

DylanDylann commented Feb 10, 2026

Uh oh!

DylanDylann commented Feb 10, 2026

Uh oh!

shawnborton commented Feb 10, 2026

Uh oh!

DylanDylann Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented Feb 10, 2026

Uh oh!

DylanDylann commented Feb 24, 2026

Uh oh!

DylanDylann commented Feb 24, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer Feb 24, 2026

Choose a reason for hiding this comment

Uh oh!

nkdengineer commented Feb 24, 2026

Uh oh!

Uh oh!

DylanDylann commented Feb 24, 2026

Uh oh!

codecov bot commented Feb 5, 2026 •

edited by github-actions bot

Loading

DylanDylann commented Feb 9, 2026 •

edited

Loading

DylanDylann commented Feb 24, 2026 •

edited

Loading