Skip to content

Replace @react-native-community/geolocation with expo-location#73757

Merged
AndrewGable merged 39 commits intoExpensify:mainfrom
software-mansion-labs:@GCyganek/expo-location-migration
Dec 11, 2025
Merged

Replace @react-native-community/geolocation with expo-location#73757
AndrewGable merged 39 commits intoExpensify:mainfrom
software-mansion-labs:@GCyganek/expo-location-migration

Conversation

@GCyganek
Copy link
Contributor

@GCyganek GCyganek commented Oct 29, 2025

Explanation of Change

With expo-location and desktop deprecation we now have only one implementation for both native and web

getCurrentPosition's API is similar to https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/getCurrentPosition as it was until now to keep the usages without changes. #74328

Usages of getCurrentPosition are in:

  • src/components/AddressSearch/index.tsx
  • src/components/MapView/MapView.tsx
  • src/components/MapView/MapViewImpl.website.tsx
  • src/pages/Share/SubmitDetailsPage.tsx
  • src/pages/iou/request/step/IOURequestStepConfirmation.tsx
  • src/pages/iou/request/step/IOURequestStepScan/index.native.tsx
  • src/pages/iou/request/step/IOURequestStepScan/index.tsx

Fixed Issues

$ #73531 (comment)
PROPOSAL:
MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/13763

Tests

AddressSearch:

  1. FAB > Track distance
  2. Click on Start
  3. Click on Use current location and verify that it works correctly

MapView & MapViewImpl:

  1. FAB > Track distance
  2. Verify that map's initial location loads successfully based on your location

IOURequestStepConfirmation:

Make sure location was never asked for on your account, otherwise it will skip the location request and use the saved one

  1. FAB > Create expense
  2. Scan > Choose files
  3. Choose a receipt that has only amount without specifying a currency

You can use this one that I was using for testing:
Screenshot 2025-10-23 at 13 33 27

  1. Submit and wait for it to request your location to get the correct currency (after scanning completes). Verify that it's working correctly

IOURequestStepScan:

Make sure location permission is granted on your device for the app/web page

  1. FAB > Create expense > Scan and submit an expense to yourself (selfDM - requires an account with Track and budget expenses chosen for What do you want to do today? onboarding step)
  2. Click on FAB and click on quick action which should be Scan receipt and add another expense using Scan that has only amount specified without a currency
  3. After scanning of the newly created expense finishes the currency should be set correctly based on the location

SubmitDetailsPage:

  1. Open a receipt photo on your phone and use Share functionality and choose Expensify
  2. Change tab to Submit and choose a contact
  3. Click on Create expense and approve location request, it should set the currency of the expense based on your location after scanning ends
  • 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]."

Same as tests

  • 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
    • MacOS: Desktop
  • 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

SubmitDetailsPage:

Screen.Recording.2025-11-04.at.12.16.44.mov

AddressSearch & MapView:

Screen.Recording.2025-11-04.at.12.21.51.mov

IOURequestStepConfirmation (location was set to US and location permission was granted to the app before):

Screen.Recording.2025-11-04.at.12.25.43.mov

IOURequestStepScan:

Screen.Recording.2025-11-04.at.14.00.27.mov
Android: mWeb Chrome
iOS: Native

AddressSearch & MapView:

Screen.Recording.2025-11-04.at.14.41.00.mov

SubmitDetailsPage:

Screen.Recording.2025-11-04.at.11.43.36.mov

IOURequestStepScan:

Screen.Recording.2025-11-04.at.15.27.12.mov

IOURequestStepConfirmation:

Screen.Recording.2025-11-04.at.15.26.31.mov
iOS: mWeb Safari
MacOS: Chrome / Safari

AddressSearch & MapView & MapViewImpl:

Screen.Recording.2025-11-03.at.17.50.01.mov

IOURequestStepConfirmation:

Screen.Recording.2025-11-03.at.18.25.28.mov

IOURequestStepScan:

Screen.Recording.2025-11-04.at.15.18.01.mov

@github-actions
Copy link
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

@codecov
Copy link

codecov bot commented Nov 3, 2025

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

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

@github-actions

This comment has been minimized.

@GCyganek GCyganek requested a review from war-in November 6, 2025 10:45
@GCyganek GCyganek marked this pull request as ready for review November 6, 2025 11:39
@GCyganek GCyganek requested review from a team as code owners November 6, 2025 11:39
@AndrewGable
Copy link
Contributor

Are we OK to merge this before the Mobile-Expensify PR is merged?

@mountiny
Copy link
Contributor

mountiny commented Dec 3, 2025

The QA is not fully done yet, I am creating a new build here and they will run through the last few cases there https://expensify.slack.com/archives/C9YU7BX5M/p1764768065649599?thread_ts=1764005101.693779&cid=C9YU7BX5M

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

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

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #73757 Mobile-Expensify PR Expensify/Mobile-Expensify#13763.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/73757/index.html ❌ FAILED ❌
Android The QR code can't be generated, because the iOS build failed
Web 🕸️
https://73757.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@mountiny
Copy link
Contributor

mountiny commented Dec 4, 2025

@GCyganek @AndrewGable the qa is done here, only one issue found

@GCyganek
Copy link
Contributor Author

GCyganek commented Dec 4, 2025

@GCyganek @AndrewGable the qa is done here, only one issue found

Could you elaborate what's the issue so I can take a look and fix it?

@AndrewGable
Copy link
Contributor

@GCyganek
Copy link
Contributor Author

GCyganek commented Dec 5, 2025

Here is the issue reported by QA

Hmmm this one should be fixed already, @jponikarchuk could you confirm?

@jponikarchuk
Copy link

@GCyganek This issue is not reproducible now

};

type GeolocationOptions = {
/** Desktop only */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have desktop anymore, so maybe this is web only?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise, let's remove

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is desktop only, so I should've removed it, but I missed it, thank you!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have also moved locationPermission.ts file content to desktop/main.ts as it was only used there to not miss deleting it when desktop/main.ts is removed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But there should be no change in how things work as I only removed desktop related code

@melvin-bot
Copy link

melvin-bot bot commented Dec 10, 2025

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@AndrewGable AndrewGable merged commit 6db192d into Expensify:main Dec 11, 2025
38 checks passed
@OSBotify
Copy link
Contributor

✋ 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
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #73757 Mobile-Expensify PR Expensify/Mobile-Expensify#13763.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/73757/index.html ❌ FAILED ❌
Android The QR code can't be generated, because the iOS build failed
Web 🕸️
https://73757.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/AndrewGable in version: 9.2.78-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.78-8 🚀

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

@situchan
Copy link
Contributor

@GCyganek Have you ever faced this error? How to fix it? I am trying to build HybridApp.

build error

@GCyganek
Copy link
Contributor Author

GCyganek commented Dec 22, 2025

@GCyganek Have you ever faced this error? How to fix it? I am trying to build HybridApp.

build error

It looks like it's trying to import react-native-android-location-enabler library which is not installed. This shouldn't happen as there are no usages of this library anymore in the code and I've removed it from package.json. Check if you have some local changes that import this library.

let message = 'Geolocation call failed';
let code = GeolocationErrorCode.POSITION_UNAVAILABLE;

if (caughtError instanceof GeolocationPositionError) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GeolocationPositionError is web-only api so it crashes on native, which led to #79230.
Fixed here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants