Filter recent waypoints with missing coordinates to prevent Null Island error

[MelvinBot]

Explanation of Change

Waypoints saved while offline may lack lat/lng values (the backend fills them in later). The recentWaypointsSelector was converting these null/undefined coordinates to 0 via the nullish coalescing operator (?? 0), creating Null Island coordinates (lat=0, lng=0). When users then selected these waypoints from the recent suggestions list, the isWaypointNullIsland check would trigger a "Please select a valid address" error.

This change adds a filter to exclude waypoints without valid lat/lng from the recent waypoints list, so they won't appear as selectable options that produce errors.

Fixed Issues

$ #82852

PROPOSAL: #82852 (comment)

Tests

1. Create a distance expense while offline with waypoints (e.g., two addresses)
2. Save the expense
3. Start creating a new distance expense
4. Tap the start or stop waypoint field
5. Verify that the recent waypoints list does NOT show the offline-saved waypoints (since they lack coordinates)
6. Go online and repeat — waypoints with resolved coordinates should appear in the list and be selectable without error

• Verify that no errors appear in the JS console

Offline tests

1. Go offline
2. Create a distance expense with waypoints and save
3. Start a new distance expense
4. Verify the recently saved (offline) waypoints do NOT appear in the recent waypoints suggestions
5. Go back online
6. After the backend resolves coordinates, verify those waypoints appear correctly in future suggestions

QA Steps

1. On a device, create a distance expense while offline with two waypoints
2. Save the expense
3. Start creating a new distance expense
4. Tap a waypoint field and check the recent suggestions
5. Verify the offline waypoints (without coordinates) do NOT appear in the suggestions list
6. Go online, wait for the backend to fill in the coordinates
7. Create another distance expense and verify the waypoints now appear in the suggestions and can be selected without error

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

Screenshots/Videos

Android: Native

N/A - Logic-only change, no UI modifications

Android: mWeb Chrome

N/A - Logic-only change, no UI modifications

iOS: Native

N/A - Logic-only change, no UI modifications

iOS: mWeb Safari

N/A - Logic-only change, no UI modifications

MacOS: Chrome / Safari

N/A - Logic-only change, no UI modifications

[MelvinBot]

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-filterNullCoordinatesFromRecentWaypoints
git checkout -b claude-filterNullCoordinatesFromRecentWaypoints upstream/claude-filterNullCoordinatesFromRecentWaypoints
git push -u origin claude-filterNullCoordinatesFromRecentWaypoints

Then you can close this PR and open a new one from your fork.

[MelvinBot]

The failing check (build (developmentDebug, false)) is unrelated to this PR's code changes.

Analysis: The failure occurred in the "Configure AWS Credentials" step with a transient DNS resolution error: getaddrinfo EAI_AGAIN sts.us-east-1.amazonaws.com. This is a GitHub Actions infrastructure issue — the runner couldn't resolve the AWS STS endpoint.

Evidence: This PR only modifies src/pages/iou/request/step/IOURequestStepWaypoint.tsx. The failure happened before any project code was built or tested.

I'll re-run the failed job.

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
.../pages/iou/request/step/IOURequestStepWaypoint.tsx	0.00% <0.00%> (ø)
... and 11 files with indirect coverage changes

[abzokhattab]

mark the pr as ready @MelvinBot

[abzokhattab]

@MelvinBot remerge from main

[MelvinBot]

Done! PR has been marked as ready for review.

[melvin-bot]

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

[MelvinBot]

Done! Merged main into this branch (commit 14c0340).

[abzokhattab]

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 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-03-13.at.03.25.59.mov

Android: mWeb Chrome

Screen.Recording.2026-03-13.at.03.28.26.mov

iOS: HybridApp

Screen.Recording.2026-03-13.at.03.23.17.mov

iOS: mWeb Safari

Screen.Recording.2026-03-13.at.03.30.27.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-13.at.03.21.10.mov

[melvin-bot]

We did not find an internal engineer to review this PR, trying to assign a random engineer to #82852 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

[melvin-bot]

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

[MelvinBot]

The failing check test (job 7) is unrelated to this PR's changes.

Failing test: tests/ui/components/IOURequestStepConfirmationPageTest.tsx — should route unreported distance expense to requestMoney and skip createDistanceRequest

Error: TypeError: Cannot read properties of undefined (reading 'GRANTED') at __mocks__/react-native-permissions.ts:11

Root cause: The newly introduced mock file __mocks__/react-native-permissions.ts (added to main in commit 0f18131 via #85129) imports RESULTS from the wrong path:

import {PERMISSIONS, RESULTS} from 'react-native-permissions/dist/commonjs/permissions';

However, that module only exports PERMISSIONS. RESULTS is actually exported from react-native-permissions/dist/commonjs/results. Since RESULTS is undefined, accessing RESULTS.GRANTED throws the TypeError.

Evidence: This PR only modifies src/pages/iou/request/step/IOURequestStepWaypoint.tsx, which is completely unrelated to the permissions mock or the confirmation page test.

Fix needed on main: Change the import in __mocks__/react-native-permissions.ts to:

import {PERMISSIONS} from 'react-native-permissions/dist/commonjs/permissions';
import {RESULTS} from 'react-native-permissions/dist/commonjs/results';

This will affect all PRs that merge from main until the import is corrected.

[MelvinBot]

I don't have permission to rerun GitHub Actions workflows. You can rerun the failed test (job 7) check yourself by visiting the workflow run and clicking Re-run failed jobs.

[abzokhattab]

remerge from main or push an empty commit to retrigger the pipeline @MelvinBot

[MelvinBot]

Pushed an empty commit to retrigger the CI pipeline.

[MelvinBot]

The failing check (test (job 7)) is unrelated to this PR's changes.

Failing test: tests/ui/components/IOURequestStepConfirmationPageTest.tsx
Error: TypeError: Cannot read properties of undefined (reading 'GRANTED') in __mocks__/react-native-permissions.ts:11

Why it's unrelated:

• This PR only modifies src/pages/iou/request/step/IOURequestStepWaypoint.tsx — a different file from what the failing test covers (IOURequestStepConfirmation)
• The same test failure (IOURequestStepConfirmationPageTest.tsx with the identical RESULTS.GRANTED error) is also occurring on completely unrelated PR Improve RTER messaging and add submit confirmation for pending card matches #85167, confirming this is a pre-existing issue on main
• The root cause is a broken import in __mocks__/react-native-permissions.ts where RESULTS from react-native-permissions/dist/commonjs/permissions resolves to undefined — this is not related to any waypoint filtering logic

No code changes are needed on this PR to address this failure.

[JmillsExpensify]

No product review required.

[abzokhattab]

remerge from main @MelvinBot

[MelvinBot]

Done! Merged main into this branch. The merge completed cleanly with no conflicts.

[OSBotify]

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

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

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-9e06f79-dd02104-f3c3b578cecfe90ccc3255303ca0dcb3ac4682a1/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-9e06f79-dd02104-47fc78cf1b1cc98f8f7448c34594bd14ae5522c4/index.html

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

---

👀 View the workflow run that generated this build 👀