[GPS] Pause/Resume functionality by GCyganek · Pull Request #88609 · Expensify/App

GCyganek · 2026-04-23T15:37:35Z

Explanation of Change

gpsPoints in GpsDraftDetails changed from 1D array to 2D array of segments. Each paused-and-resumed section of a trip becomes a separate segment.
startAddress and endAddress top-level fields removed from GpsDraftDetails. Address is now stored directly on each GPSPoint as an optional address field, so each segment carries its own start/end address.
Stopping tracking no longer ends the trip — it moves to a "stopped" state. The user can then resume (starts a new segment) or save (submits the trip).
resumeGpsTrip action adds a new empty segment to gpsPoints and sets isTracking: true. The background location task automatically resolves the start address for the new segment when the first point arrives.
The stop confirmation modal has been removed. Stop is now immediate; discard has moved to a dedicated trash icon button (DiscardGPSTripButton) shown only in the stopped state.
The "Stop" button's danger style removed; the "Discard" button replaced with "Resume"; the "Next" button replaced with "Save".
directionCoordinates in MapViewProps and DirectionProps updated to accept Coordinate[] | Coordinate[][].
Direction.tsx renders separate ShapeSource/LineLayer pairs for each segment, preserving the visual gap between paused segments on the map.
MapView.tsx and MapViewImpl.website.tsx flatten multi-segment coordinates for bounds/centering calculations only, while passing the original segmented array to Direction.
ConvertGpsPointsTo2DArray migration wraps any old existing gpsPoints into an additional array to make it 2D and migrates startAddress/endAddress values into the address field on the first and last points respectively.

Fixed Issues

$ #86026
PROPOSAL: N/A

Tests

Discard button:

FAB > Track distance > GPS
Tap Start and track some distance
Verify that there is a correct route on the map as you travel
Tap Stop
Verify that Start and Stop addresses load correctly
Verify that the discard button appears next to the distance counter on the right
Tap the discard button
Verify that it shows confirm dialog
Confirm to discard the trip
Verify that it resets the state and that the trip can be started again

Multi-segment trip:

FAB > Track distance > GPS
Tap Start and track some distance
Verify that there is a correct route on the map as you travel
Tap Stop
Verify that Start and Stop addresses have loaded correctly
Tap Resume after a while to continue the trip from a different location
Verify that the trip resumes and the Stop address is replaced with Tracking distance... and there is a new separate segment of the trip on the map
Tap Stop again
Verify that the Stop address loads correctly
Tap Save and select a Workspace
Verify that the expense is created successfully
Open the generated receipt
Verify that the receipt is correct and that it shows Stop/Start waypoints for all segments of the trip
Repeat, but create selfDM expense this time

Single segment trip:

FAB > Track distance > GPS
Tap Start and track some distance
Verify that there is a correct route on the map as you travel
Tap Stop
Verify that Start and Stop addresses have loaded correctly
Tap Save and select a Workspace
Verify that the expense is created successfully
Open the generated receipt
Verify that the receipt is correct and that it shows Stop/Start waypoints for all segments of the trip
Repeat, but create selfDM expense this time

Verify that no errors appear in the JS console

Offline tests

Start a trip in offline mode
Pause and resume a trip a few times to make sure that the trip will be segmented
Verify that Stop/Start waypoints have coordinates instead of human readable addresses
Stop the trip
Go online
Verify that Stop/Start waypoints have human readable addresses instead of coordinates
Submit the trip
Open the generated receipt
Verify that the Start/Stop waypoints have human readable addresses

QA Steps

Same as tests

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2026-05-04.at.15.48.17.mov

Screen.Recording.2026-05-04.at.15.49.15.mov

Screen.Recording.2026-05-04.at.17.35.53.mov

Screen.Recording.2026-05-04.at.17.37.12.mov

iOS: Native

Screen.Recording.2026-05-04.at.17.54.18.mov

Screen.Recording.2026-05-04.at.17.55.40.mov

Screen.Recording.2026-05-04.at.17.56.22.mov

Screen.Recording.2026-05-04.at.17.57.37.mov

melvin-bot · 2026-04-23T15:37:41Z

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

Look at the code and make sure there are no malicious changes.
Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

codecov · 2026-04-23T15:49:01Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/components/GPSInProgressModal/index.native.tsx	`100.00% <100.00%> (ø)`
...rc/components/GPSTripStateChecker/index.native.tsx	`73.68% <100.00%> (+0.71%)`	⬆️
src/components/MapView/utils.ts	`31.74% <100.00%> (+2.23%)`	⬆️
src/libs/getArrayDepth.ts	`100.00% <100.00%> (ø)`
src/libs/is2dArray.ts	`100.00% <100.00%> (ø)`
src/libs/migrateOnyx.ts	`100.00% <100.00%> (+18.75%)`	⬆️
src/components/AccountSwitcher.tsx	`0.00% <0.00%> (ø)`
src/components/MapView/MapView.tsx	`56.60% <50.00%> (+0.41%)`	⬆️
.../request/step/confirmation/useExpenseSubmission.ts	`52.55% <50.00%> (ø)`
src/components/ConfirmedRoute.tsx	`0.00% <0.00%> (ø)`
... and 14 more
... and 200 files with indirect coverage changes

GCyganek · 2026-04-23T16:07:40Z

@Expensify/design the backend is not merged yet and we need to wait for it to be able to create receipts with split GPS trips, but here you can see how it will look like:

Screen.Recording.2026-04-23.at.18.00.07.mov

Of course map styles (icons and route) will be updated soon in a separate PR

shawnborton · 2026-04-23T16:13:20Z

I would think we don't need this modal, right?

Otherwise this is feeling nice!

GCyganek · 2026-04-23T16:14:21Z

I would think we don't need this modal, right?

We have it from the beginning, but I can delete it if you prefer, of course

shawnborton · 2026-04-23T16:15:57Z

Yeah now that we have a super simple way to resume if you accidentally stopped, I think we don't need it personally.

GCyganek · 2026-04-23T16:24:10Z

Will do!

dannymcclain · 2026-04-23T19:26:13Z

Yeah now that we have a super simple way to resume if you accidentally stopped, I think we don't need it personally.

Totally agree!

dubielzyk-expensify · 2026-04-27T02:47:08Z

Agree with removing the modal. That was there for safety before the pause.

Can we change the wording here a bit. The primary button for in progress should say: Pause (instead of Stop).

And then ones paused can we say Resume and Finish. I just think that soften the language a bit to ensure people know that they can start/stop at any point. And finish is a clearer way to say the journey is ending than Save.

That is if @Expensify/design team is okay with that ofc.

GCyganek · 2026-04-27T07:06:15Z

Can we change the wording here a bit. The primary button for in progress should say: Pause (instead of Stop).

And then ones paused can we say Resume and Finish. I just think that soften the language a bit to ensure people know that they can start/stop at any point. And finish is a clearer way to say the journey is ending than Save.

I like this change, will wait for confirmation before I change it here

shawnborton · 2026-04-27T08:18:33Z

I don't feel strongly. Part of me thinks it won't be common for people to pause and resume, so having the only word to "finish" your tracking be "Pause" feels a bit odd to me. I think I would personally just keep Stop but let's see how the others feel!

dannymcclain · 2026-04-27T13:45:45Z

No strong feelings from me - when I first read your updated copy I thought "Oh yeah I like that!" but then when I read Shawn's comment I did kinda feel like oh yeah, stop is more clear/expected than pause for ending my tracking. I do kinda like Finish instead of Save though, but ultimately I'm not super passionate and think either would be fine.

I also don't really use any GPS tracking apps or workflows, so I'm not familiar with what the most common patterns and verbiage are. Happy to lean on those with more experience/context!

dubielzyk-expensify · 2026-04-28T02:25:02Z

Alright, let's leave it as is then.

GCyganek · 2026-05-04T10:50:26Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 68184edd30

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

GCyganek · 2026-05-04T11:31:01Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: de02cb9ad7

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

GCyganek · 2026-05-05T07:34:40Z

Let me check that address issue. We should be showing coordinates only if fetching human readable address from coordinates fails or user's offline

EDIT: Should be fixed now

shawnborton · 2026-05-05T12:11:16Z

Tests super well! I have the same GPS starting thing that Jon reported, otherwise it seems to be great.

One thing I noticed, that is likely a separate conversation, is that I went through a tunnel with poor cell service and the map line didn't really get my path right:

You can see where it missed the road and has a triangular shape. Anything we can do about that?

GCyganek · 2026-05-05T14:28:36Z

Anything we can do about that?

Tunnels are problematic for GPS tracking as if satellite is not reachable and there is no cell service then there is no way to get location updates. If this is a real problem for us then I could do some research, but I don't have a solution at the moment unfortunately.

This actually reminds me that @JmillsExpensify is working on the option to choose alternative routes, so maybe using it user would have a way to choose the same route, but with the fixed tunnel part?

dubielzyk-expensify · 2026-05-06T03:02:35Z

How often are we adding a geolocation and spot on the polyline? Obviously I'm assuming we don't wanna add a mapping solution, but I did find it a bit jarring that, when driving, it took quite a few meters before the trip length grew. Maybe it's fine though

GCyganek · 2026-05-06T07:47:56Z

How often are we adding a geolocation and spot on the polyline? Obviously I'm assuming we don't wanna add a mapping solution, but I did find it a bit jarring that, when driving, it took quite a few meters before the trip length grew. Maybe it's fine though

We have 0.1 mi distance interval. It can be changed, but we decided to stick with it, because the longer the trip, the more points we save and we have a limit in the backend of how many points can be used to create a receipt and if we have too many points, then we have to use an algorithm which discards every n-th point to go down to the limit and makes the trip lose precision anyway

Anyway, we could try reducing the distance interval, which will make the trip updates more frequent and the only downside would be that the map with the route on the receipt generated in the backend will be less precise than what the user sees on the map while the trip is in progress and before it's saved as an expense faster (less distance needed to reach the limit when we have to use the algorithm that discards points).

dukenv0307 · 2026-05-06T14:01:35Z

on it now

dukenv0307 · 2026-05-06T14:26:50Z

+import type {GPSPoint} from '@src/types/onyx/GpsDraftDetails';

 function useUpdateGpsTripOnReconnect() {
    const [gpsDraftDetails] = useOnyx(ONYXKEYS.GPS_DRAFT_DETAILS);


I think we can remove it entirely, then use OnyxUtils.get inside updateAddressesToHumanReadable. If we still need gpsDraftDetails reactive value, we can pass it from its parent

dukenv0307 · 2026-05-06T14:46:28Z

 import type {Coordinate} from './MapViewTypes';

+function isSingleSegmentRoute(directionCoordinates: Coordinate[] | Coordinate[][]): directionCoordinates is Coordinate[] {
+    return getArrayDepth(directionCoordinates) === 2;


let's use is2dArray, or we can use is2dArray directly, no need to create isSingleSegmentRoute

I can use is2dArray in this function, but I'd leave the isSingleSegmentRoute, as it makes the code more readable IMO. Without it it can be confusing, as looking at the type Coordinate[] you'd guess it's 1d array, but it's actually a 2d array because Coordinate is [number, number], so using isSingleSegmentRoute immediately tells us that we're checking if we're using a segmented trip (3d array) or a simple trip without segments (2d array)

dukenv0307 · 2026-05-06T15:09:40Z

In useGPSWaypointMarkers.tsx

const waypointEntries = Object.entries(getGPSWaypoints(gpsDraftDetails));
    const lastIndex = waypointEntries.length - 1;

    return waypointEntries.flatMap(([key, waypoint], index): WayPoint[] => {
        const isStart = index === 0;
        const isEnd = index === lastIndex;

        if (isEnd && !isTripStopped) {
            return [];
        }

        let icon = DotIndicator;
        if (isStart) {
            icon = DotIndicatorUnfilled;
        } else if (isEnd) {
            icon = Location;
        }

        return [
            {
                id: key,
                coordinate: [waypoint.lng, waypoint.lat],
                markerComponent: (): ReactNode => getMarkerComponent(icon),
            },
        ];
    });
}

dukenv0307 · 2026-05-06T15:11:38Z

The rest looks good

GCyganek · 2026-05-07T08:16:05Z

The rest looks good

Applied changes according to the review

dukenv0307 · 2026-05-07T16:22:19Z

on it now

dukenv0307 · 2026-05-07T16:40:55Z

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-05-07.at.23.38.23.mov

Android: mWeb Chrome

iOS: HybridApp

Screen.Recording.2026-05-07.at.23.28.58.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

OSBotify · 2026-05-07T17:49:58Z

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

github-actions · 2026-05-07T18:04:13Z

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

github-actions · 2026-05-07T18:15:34Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5d094c0-593d847-ead5184f17c4b58a2f003bfd1a5c132eab9afa07/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-5d094c0-593d847-1b621ff798f2cf2fed1929c48aa96803235e50f5/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-05-08T15:41:13Z

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.69-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-05-08T15:44:36Z

Yes, help site changes are required. The GPS tracking flow changed significantly in this PR — stop is now immediate (no confirmation dialog), Resume enables multi-segment trips, Save replaces Next, and there's a new discard button.

I've created a draft PR with the necessary updates to two help site articles:

Draft PR: #90014

Files updated:

docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md — Updated GPS steps, keywords, and receipt FAQ
docs/articles/new-expensify/reports-and-expenses/Create-an-Expense.md — Updated GPS steps

Changes made:

Removed "confirm by selecting Stop GPS tracking" (confirmation modal was removed)
Added Resume step for multi-segment trips
Replaced Next with Save
Added discard trip step (trash icon)
Updated GPS receipt FAQ to mention multi-segment trip receipts
Added pause/resume keywords for search discoverability

OSBotify · 2026-05-11T23:41:42Z

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.69-18 🚀

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

[GPS] Pause/Resume functionality

f75d647

melvin-bot Bot assigned GCyganek Apr 23, 2026

Fix typescript

e39d3c6

GCyganek added 2 commits April 24, 2026 11:32

Do not show stop confirmation modal

b19268f

Merge branch 'main' into @GCyganek/gps/pause-resume-gps-trip

61e7b58

GCyganek mentioned this pull request Apr 30, 2026

Add stop address editing for GPS mileage #85802

Open

GCyganek added 6 commits April 30, 2026 09:49

Merge branch 'main' into @GCyganek/gps/pause-resume-gps-trip

2135825

Merge branch 'main' into @GCyganek/gps/pause-resume-gps-trip

8432d5a

Fix ESlint

2f6536c

Clean-up types

01c1620

Extract DiscardGPSTripButton and DistanceCounter from Waypoints

8253461

Code cleanup

68184ed

chatgpt-codex-connector Bot reviewed May 4, 2026

View reviewed changes

Comment thread src/libs/actions/GPSDraftDetails.ts Outdated

Comment thread src/components/GPSTripStateChecker/useUpdateGpsTripOnReconnect.ts Outdated

Comment thread src/components/GPSTripStateChecker/useUpdateGpsTripOnReconnect.ts Outdated

AI review feedback changes

de02cb9

chatgpt-codex-connector Bot reviewed May 4, 2026

View reviewed changes

Comment thread src/setup/backgroundLocationTrackingTask/index.native.ts Outdated

Comment thread src/components/MapView/MapViewImpl.website.tsx

GCyganek added 2 commits May 5, 2026 09:48

Fix loading start waypoint address in background task

4e31b7a

Add generated translations

62edc1f

Merge branch 'main' into @GCyganek/gps/pause-resume-gps-trip

7695f73

dukenv0307 reviewed May 6, 2026

View reviewed changes

Review feedback

3593310

dukenv0307 approved these changes May 7, 2026

View reviewed changes

melvin-bot Bot requested a review from puneetlath May 7, 2026 16:42

puneetlath approved these changes May 7, 2026

View reviewed changes

puneetlath merged commit 5d094c0 into Expensify:main May 7, 2026
39 checks passed

OSBotify mentioned this pull request May 8, 2026

Deploy Checklist: New Expensify 2026-05-08 #90006

Closed

MelvinBot mentioned this pull request May 8, 2026

[No QA] Docs updates for E/A#88609 GPS pause resume and save flow #90014

Open

QichenZhu mentioned this pull request May 12, 2026

Remove unused type exports #90245

Merged

51 tasks

Conversation

GCyganek commented Apr 23, 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!

melvin-bot Bot commented Apr 23, 2026

Uh oh!

codecov Bot commented Apr 23, 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!

GCyganek commented Apr 23, 2026

Uh oh!

shawnborton commented Apr 23, 2026

Uh oh!

GCyganek commented Apr 23, 2026

Uh oh!

shawnborton commented Apr 23, 2026

Uh oh!

GCyganek commented Apr 23, 2026

Uh oh!

dannymcclain commented Apr 23, 2026

Uh oh!

dubielzyk-expensify commented Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

GCyganek commented Apr 27, 2026

Uh oh!

shawnborton commented Apr 27, 2026

Uh oh!

dannymcclain commented Apr 27, 2026

Uh oh!

dubielzyk-expensify commented Apr 28, 2026

Uh oh!

GCyganek commented May 4, 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!

GCyganek commented May 4, 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!

GCyganek commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shawnborton commented May 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

GCyganek commented May 5, 2026

Uh oh!

dubielzyk-expensify commented May 6, 2026

Uh oh!

GCyganek commented May 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dukenv0307 commented May 6, 2026

Uh oh!

dukenv0307 May 6, 2026

Choose a reason for hiding this comment

Uh oh!

dukenv0307 May 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

GCyganek May 7, 2026

GCyganek commented Apr 23, 2026 •

edited

Loading

codecov Bot commented Apr 23, 2026 •

edited by github-actions Bot

Loading

dubielzyk-expensify commented Apr 27, 2026 •

edited

Loading

GCyganek commented May 5, 2026 •

edited

Loading

shawnborton commented May 5, 2026 •

edited

Loading

GCyganek commented May 6, 2026 •

edited

Loading

dukenv0307 May 6, 2026 •

edited

Loading