[Due for payment 2026-01-27] [$250] Refactor WorkspaceReceiptPartnersPage loading component

[Julesssss]

Details

We recently improved the FullscreenLoadingIndicator by displaying a back button after 10 seconds to provide a recovery path in case of infinite loading.

The WorkspaceReceiptPartnersPage component appears to be a case where we should now be using FullscreenLoadingIndicator instead of ActivityIndicator. It looks like we render this before HeaderWithBackButton is displayed, so there is a chance that the user gets stuck.

Parent issue with more context.

Solution

Verify this is the case and refactor the component to use FullScreenLoadingIndicator. to provide an escape recovery mechanism for users.

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022009684263007938026
• Upwork Job ID: 2009684263007938026
• Last Price Increase: 2026-01-09
• Automatic offers:
• samranahm | Contributor | 110081591

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @RachCHopkins

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022009684263007938026

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 (External)

[Eskalifer1]

I would like to work on this

PS: I don't think a proposal is needed here, as the solution is already described in the OP, and similar tasks were done some time ago and no proposal was needed there either. Here is a similar task that I worked on, only here I had to perform the opposite actions. The proposal was not needed. #75534

[samranahm]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The WorkspaceReceiptPartnersPage component currently uses ActivityIndicator to show loading state while fetching receipt partner data. If the API call hangs or takes excessively long, users become stuck on a blank loading screen with no way to navigate back, creating a poor user experience.

What is the root cause of that problem?

The component renders ActivityIndicator during the initial data load, and only displays HeaderWithBackButton (containing back navigation) once loading completes. This creates a gap where users are stuck on a loading screen without any visible escape route if the API call hangs or times out. The recently improved FullscreenLoadingIndicator provides a "Go Back" button after 10 seconds to address exactly this scenario, but the component is not using it.

What changes do you think we should make in order to solve the problem?

Replace ActivityIndicator with FullscreenLoadingIndicator and enable the back button recovery mechanism.
Update the loading state rendering to use FullscreenLoadingIndicator with shouldUseGoBackButton={true}

<FullscreenLoadingIndicator
    shouldUseGoBackButton={true}

here

App/src/pages/workspace/receiptPartners/WorkspaceReceiptPartnersPage.tsx

Lines 247 to 251 in 75a8599

	{isLoading ? (
	<ActivityIndicator
	size={CONST.ACTIVITY_INDICATOR_SIZE.LARGE}
	style={styles.flex1}
	/>

What alternative solutions did you explore? (Optional)

N/A

[PiyushChandra17]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Refactor WorkspaceReceiptPartnersPage loading component

What is the root cause of that problem?

Use FullScreenLoadingIndicator instead of ActivityIndicator in WorkspaceReceiptPartnersPage

What changes do you think we should make in order to solve the problem?

Replace ActivityIndicator with FullScreenLoadingIndicator

• <FullScreenLoadingIndicator style={[styles.flex1]}/>

What alternative solutions did you explore? (Optional)

n/A

Result

WorkspaceReceiptPartnersPage-fs.mov

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.