Fix: Replace FullScreenLoadingIndicator with ActivityIndicator in AddressSearch Component

[PiyushChandra17]

Explanation of Change

Replace FullScreenLoadingIndicator with ActivityIndicator in AddressSearch Component

Fixed Issues

$ #75535
PROPOSAL: #75535(Comment)

Tests

Test case 1:

1. Open the New Expensify App
2. Tap on FAB > Go to "Track distance"
3. Tap on "Start" waypoint
4. On "Address" input field > Tap on "Use current location"
5. Verify the display of Loading is correct

Test case 2:

1. Open the New Expensify App
2. Click on "Accounts" tab
3. Go to "Subscription"
4. Tap on "Add payment card"
5. This PaymentCardForm uses AddressSearch component > Verify the display of Loading is correct

Test case 3:

1. Open the New Expensify app
2. Click on "Account" tab
3. Go to "Profile"
4. Tap on "Address" input field
5. Verify the display of Loading is correct

Test case 4:

1. Open the New Expensify App
2. Click on "Workspaces" tab
3. Click on "Workspaces" name
4. Go to "Overview" > Tap on "Company Address" input field
5. Verify the display of Loading is correct

Test case 5:

1. Open the New Expensify App
2. Click on "Account" tab
3. Go to "Wallet" > Tap on "Add bank account"
4. Click on "Next"
5. On Add Bank account page > Fill all the input fields > Tap on "Next" button > Savings > Confirm
6. On Bank information page > On "Bank Address" input field > Verify the display of Loading is correct
7. Tap on "Next" button
8. On Account holder information page > On "Bank Address" input field > Verify the display of Loading is correct

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

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
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

android-mweb-chrome-td-ai.mov

android-mweb-chrome-activity-indicator.mov

android-mweb-chrome-personaladdress-activity-indicator.mov

android-mweb-chrome-worspace-overview-ai.mov

android-mweb-chrome-wallet-ba-ai.mov

iOS: Native

iOS: mWeb Safari

ios-mweb-safari-td-ai.mov

ios-mweb-safari-activity-indicator.mov

ios-mweb-safari-personaladdress-activity-indicator.mov

ios-mweb-safari-workspaceoverview-ai.mov

ios-mweb-safari-wallet-ba-ai.mov

MacOS: Chrome / Safari

macos-chrome-td-ai.mov

macos-chrome-activity-indicator.mov

macos-chrome-personaladress-activity-indicator.mov

macos-chrome-workspace-overview-ai.mov

macos-chrome-wallet-ba-ai.mov

MacOS: Desktop

macos-desktop-td01-ai.mov

macos-desktop-activity-indicator.mov

macos-desktop-personaladdress-activity-indicator.mov

macos-desktop-workspace-overview-ai.mov

macos-desktop-wallet-ba-ai.mov

[melvin-bot]

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

[melvin-bot]

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

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/components/AddressSearch/index.tsx	48.03% <100.00%> (ø)
... and 19 files with indirect coverage changes

[Julesssss]

Hi @PiyushChandra17, could you please add further test cases to verify other uses are also working as expected, thanks:

• Settings > Profile > Personal Details > Address
• Settings > Wallet > Cards > Digital Details > Update Address
• Workspace > Bank account setup > Bank Account Details
• Workspace > Settings > Overview > Address
• Create distance expense > Add/edit waypoint
• Settings > Subscription > Add payment card

[PiyushChandra17]

@Julesssss I think i had already added 2 test cases, i think that's enough. It's pretty self-explanatory that other test cases uses will also work perfectly the same. Let me know wdyt? Also do you want me to update screenshots/recordings of all remaining test cases mentioned ^. Thanks!

[PiyushChandra17]

could you please add further test cases to verify other uses are also working as expected

@Julesssss Yeah it does make sense to add all test cases to verify the loader is working as expected in other parts aswell. Will do that tomm. morning first time at the desk .. Thanks!

[Krishna2323]

Use CONST.ACTIVITY_INDICATOR_SIZE.LARGE.

[PiyushChandra17]

@Krishna2323 exactly i was thinking the same, thanks

[Krishna2323]

@PiyushChandra17 the UI interactivity is not the same as before, now I can interact with the input and the loader position is also not fixed. Also, the background opacity/color is also changed.

FullScreenLoadingIndicator

Monosnap.screencast.2025-11-28.13-43-22.mp4

ActivityIndicator

Monosnap.screencast.2025-11-28.13-44-05.mp4

[PiyushChandra17]

now I can interact with the input

@Krishna2323 I think we need apply style={[styles.h100]} in order to fix this (i did applied this style originally).

[Krishna2323]

We should change the component to ActivityIndicator while keeping the current design.

@PiyushChandra17 please make sure that it looks the same as before.

[github-actions]

🚧 @Julesssss 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 #76156.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/76156/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/76156/index.html

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

---

👀 View the workflow run that generated this build 👀

[Krishna2323]

@PiyushChandra17 it still doesn't look the same:

FullScreenLoadingIndicator

Monosnap.screencast.2025-11-30.12-19-37.mp4

ActivityIndicator

Monosnap.screencast.2025-11-30.12-19-14.mp4

[PiyushChandra17]

it still doesn't look the same

@Krishna2323 Can you please check once again

Current FullScreenLoadingIndicator

current-search-address01-fullscreenloadingindicator.mov

Latest-styling-change-ActivityIndicator

up-to-date-search-address-activity-indicator.mov

[Krishna2323]

@PiyushChandra17 the bg is still not transparent.

[PiyushChandra17]

@Krishna2323 What do you mean by background still not being transparent?

[Krishna2323]

@PiyushChandra17 in the current FullScreenLoadingIndicator, you can still see the input behind it, but in the updated ActivityIndicator, the input is not visible (there’s no opacity on the background).