[Payment due @ZhenjaHorbach] [NoQA] Consume isLockedToNewApp and block OldApp escape hatches by inimaga · Pull Request #87101 · Expensify/App

inimaga · 2026-04-03T15:55:25Z

Explanation of Change

This PR updates App to consume the new tryNewDot.isLockedToNewApp mobile-only lock signal end to end.

It adds the field to the App-side TryNewDot contract, makes the HybridApp decision logic keep locked users in NewApp, blocks closeReactNativeApp({shouldSetNVP: true}) handoffs when the mobile lock is enabled, and hides the known Hybrid OldApp escape hatches in settings, troubleshoot, merge-accounts, and the Classic confirmation modal.

It also adds focused tests covering the shared lock logic, blocked Hybrid exits, and the modal visibility gating.

Fixed Issues

$https://github.com/Expensify/Expensify/issues/619799
PROPOSAL: N/A

Tests

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]."

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 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.
I verified that similar component doesn't exist in the codebase
I verified that all props are defined accurately and each prop has a /** comment above it */
I verified that each file is named correctly
I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
I verified that the only data being stored in component state is data necessary for rendering and nothing else
In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
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)
I verified that component 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)
I verified that all JSX used for rendering exists in the render method
I verified that each 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

Screenshots/Videos

N/A

codecov · 2026-04-03T16:03:36Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...Modal/BaseConfirmNavigateExpensifyClassicModal.tsx	`90.90% <100.00%> (+2.02%)`	⬆️
src/components/ScreenWrapper/index.tsx	`88.63% <100.00%> (+0.40%)`	⬆️
src/components/SplashScreenHider/index.native.tsx	`100.00% <100.00%> (ø)`
src/libs/HybridApp.ts	`54.16% <ø> (+4.16%)`	⬆️
src/libs/actions/HybridApp/index.ts	`60.00% <100.00%> (+60.00%)`	⬆️
.../home/SpendOverTimeSection/useSpendOverTimeData.ts	`0.00% <ø> (ø)`
...ges/inbox/sidebar/FABPopoverContent/FABButtons.tsx	`100.00% <100.00%> (ø)`
...FABPopoverContent/useRedirectToExpensifyClassic.ts	`81.81% <100.00%> (+19.31%)`	⬆️
...ts/AddressSearch/isCurrentTargetInsideContainer.ts	`0.00% <0.00%> (ø)`
src/components/PopoverProvider/index.tsx	`0.00% <0.00%> (ø)`
... and 11 more
... and 15 files with indirect coverage changes

melvin-bot · 2026-04-05T22:20:21Z

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e01468912e

ℹ️ 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/libs/actions/HybridApp/index.ts

src/libs/TryNewDotUtils.ts

joekaufmanexpensify

Core design doc PR

github-actions · 2026-04-07T08:20:57Z

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

ZhenjaHorbach · 2026-04-07T08:27:19Z

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

Screenrecorder-2026-04-07-14-03-30-791.mp4

Android: mWeb Chrome

NA

iOS: HybridApp

Screenrecorder-2026-04-07-14-03-30-791.mp4

iOS: mWeb Safari

NA

MacOS: Chrome / Safari

2026-04-07.12.31.40.mov

src/pages/inbox/sidebar/FABPopoverContent/menuItems/CreateReportMenuItem.tsx

src/pages/inbox/sidebar/FABPopoverContent/menuItems/ExpenseMenuItem.tsx

src/pages/inbox/sidebar/FABPopoverContent/menuItems/InvoiceMenuItem.tsx

src/pages/inbox/sidebar/FABPopoverContent/menuItems/TrackDistanceMenuItem.tsx

inimaga · 2026-04-07T14:56:25Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e87936535

ℹ️ 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/libs/actions/HybridApp/index.ts

inimaga · 2026-04-07T15:21:28Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5e73b671e1

ℹ️ 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/pages/home/SpendOverTimeSection/useSpendOverTimeData.ts

inimaga · 2026-04-07T15:37:23Z

@codex review

chatgpt-codex-connector · 2026-04-07T15:54:58Z

Codex Review: Didn't find any major issues. Breezy!

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

inimaga · 2026-04-07T15:55:07Z

@ZhenjaHorbach I found a few additional OldApp escape hatches that I've patched. Please re-review.

ZhenjaHorbach · 2026-04-07T15:56:03Z

@ZhenjaHorbach I found a few additional OldApp escape hatches that I've patched. Please re-review.

Sure!
But could you please run adhoc builds?

github-actions · 2026-04-07T15:58:50Z

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

github-actions · 2026-04-07T16:03:43Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ef9d948-c55fd38-c6ee6fd7f772485045f1c85b226ef1659ba3dbd6/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ef9d948-c55fd38-3e8921ae0c4155aa2d3e4412d8a82759cd2dc8b8/index.html

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

👀 View the workflow run that generated this build 👀

ZhenjaHorbach · 2026-04-08T14:08:21Z

LGTM!

aldo-expensify · 2026-04-08T18:12:32Z

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

QA section is incomplete

ZhenjaHorbach · 2026-04-08T18:14:18Z

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

QA section is incomplete

But we have [No QA] 😅

aldo-expensify · 2026-04-08T18:29:08Z

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

QA section is incomplete

But we have [No QA] 😅

haha I missed it 🙈

github-actions · 2026-04-08T18:30:23Z

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

github-actions · 2026-04-08T18:35:14Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-9f28f75-77157b8-a18fb4530859148d3f4a352c390730bfdb066fc8/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-9f28f75-77157b8-a1df5cc394215b2829f94b1402aaea1ef2f2c1dc/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-04-08T18:38:26Z

✋ 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-09T00:58:06Z

🚀 Deployed to staging by https://github.com/aldo-expensify in version: 9.3.55-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-04-09T01:06:57Z

Yes, changes are required to the help site. PR #87101 introduces isLockedToNewApp, a mobile-only lock that hides the option to switch to Expensify Classic. Three help articles referenced switching to Classic without mentioning this new scenario.

Draft PR created: #87437

Articles updated:

Switch-between-New-Expensify-and-Expensify-Classic.md — Added mobile lock as a reason the switch option may not appear; updated FAQ answers
Merge-Accounts.md — Added note that Classic switch is unavailable when account is locked to new mobile app
Two-Factor-Authentication.md — Added guidance to use web version when mobile account is locked

Please mark the PR as "Ready for review" when it looks good.

inimaga added 3 commits April 3, 2026 16:51

Add mobile lock plumbing

a907f0b

Hide Classic exits

24a7332

Add mobile lock tests

e014689

melvin-bot bot assigned inimaga Apr 3, 2026

inimaga marked this pull request as ready for review April 5, 2026 22:20

inimaga requested review from a team as code owners April 5, 2026 22:20

melvin-bot bot requested a review from ZhenjaHorbach April 5, 2026 22:20

melvin-bot bot requested review from joekaufmanexpensify and removed request for a team April 5, 2026 22:20

inimaga changed the title ~~Consume isLockedToNewApp and block OldApp escape hatches~~ [NoQA] Consume isLockedToNewApp and block OldApp escape hatches Apr 5, 2026

chatgpt-codex-connector bot reviewed Apr 5, 2026

View reviewed changes

src/libs/actions/HybridApp/index.ts Outdated Show resolved Hide resolved

ZhenjaHorbach reviewed Apr 6, 2026

View reviewed changes

src/libs/TryNewDotUtils.ts Outdated Show resolved Hide resolved

ZhenjaHorbach reviewed Apr 6, 2026

View reviewed changes

src/libs/TryNewDotUtils.ts Outdated Show resolved Hide resolved

joekaufmanexpensify previously approved these changes Apr 6, 2026

View reviewed changes

inimaga added 2 commits April 6, 2026 22:26

Merge branch 'main' into issa/consume-isLockedToNewApp

a5ebb7f

Hide blocked FAB Classic redirect flows

26cea27

inimaga dismissed joekaufmanexpensify’s stale review via 26cea27 April 6, 2026 21:47

address review comment

c9de71d

This comment has been minimized.

Sign in to view

Fix typecheck in redirect test

8470734

ZhenjaHorbach reviewed Apr 7, 2026

View reviewed changes

src/pages/inbox/sidebar/FABPopoverContent/menuItems/CreateReportMenuItem.tsx Show resolved Hide resolved

ZhenjaHorbach reviewed Apr 7, 2026

View reviewed changes

src/pages/inbox/sidebar/FABPopoverContent/menuItems/ExpenseMenuItem.tsx Show resolved Hide resolved

ZhenjaHorbach reviewed Apr 7, 2026

View reviewed changes

src/pages/inbox/sidebar/FABPopoverContent/menuItems/InvoiceMenuItem.tsx Show resolved Hide resolved

ZhenjaHorbach reviewed Apr 7, 2026

View reviewed changes

src/pages/inbox/sidebar/FABPopoverContent/menuItems/TrackDistanceMenuItem.tsx Show resolved Hide resolved

Block further HybridApp exits to OldApp

be9a1a3

inimaga added 2 commits April 7, 2026 15:57

Merge branch 'main' into issa/consume-isLockedToNewApp

7e87936

Fix typecheck and eslint issues

f6c9c8c

chatgpt-codex-connector bot reviewed Apr 7, 2026

View reviewed changes

src/libs/actions/HybridApp/index.ts Outdated Show resolved Hide resolved

Address codex blocker and fix lint

5e73b67

Fix spend over time search refetch loop

ef9d948

chatgpt-codex-connector bot reviewed Apr 7, 2026

View reviewed changes

src/pages/home/SpendOverTimeSection/useSpendOverTimeData.ts Outdated Show resolved Hide resolved

ZhenjaHorbach approved these changes Apr 8, 2026

View reviewed changes

aldo-expensify approved these changes Apr 8, 2026

View reviewed changes

aldo-expensify merged commit 9f28f75 into main Apr 8, 2026
38 checks passed

aldo-expensify deleted the issa/consume-isLockedToNewApp branch April 8, 2026 18:29

OSBotify mentioned this pull request Apr 9, 2026

Deploy Checklist: New Expensify 2026-04-09 #87435

Open

62 tasks

MelvinBot mentioned this pull request Apr 9, 2026

[No QA] Update help docs for isLockedToNewApp mobile lock #87437

Draft

53 tasks

Conversation

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

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov bot commented Apr 3, 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 Apr 5, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

joekaufmanexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

This comment has been minimized.

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

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

inimaga commented Apr 7, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

inimaga commented Apr 7, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

inimaga commented Apr 7, 2026

Uh oh!

chatgpt-codex-connector bot commented Apr 7, 2026

Uh oh!

inimaga commented Apr 7, 2026

Uh oh!

ZhenjaHorbach commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

github-actions bot commented Apr 7, 2026

Uh oh!

ZhenjaHorbach commented Apr 8, 2026

Uh oh!

aldo-expensify commented Apr 8, 2026

Uh oh!

ZhenjaHorbach commented Apr 8, 2026

Uh oh!

aldo-expensify commented Apr 8, 2026

Uh oh!

Uh oh!

github-actions bot commented Apr 8, 2026

Uh oh!

github-actions bot commented Apr 8, 2026

Uh oh!

OSBotify commented Apr 8, 2026

Uh oh!

inimaga commented Apr 3, 2026 •

edited

Loading

codecov bot commented Apr 3, 2026 •

edited by github-actions bot

Loading

ZhenjaHorbach commented Apr 7, 2026 •

edited

Loading