You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-01-27] [$250] Refactor WorkspaceReceiptPartnersPage loading component #79225
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 FullscreenLoadingIndicatorinstead of ActivityIndicator. It looks like we render this before HeaderWithBackButton is displayed, so there is a chance that the user gets stuck.
changed the title [-]Refactor WorkspaceReceiptPartnersPage loading component[/-][+][$250] Refactor WorkspaceReceiptPartnersPage loading component[/+]on Jan 9, 2026
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
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}
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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Issue is ready for payment but no BZ is assigned. @RachCHopkins you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
Activity
[-]Refactor WorkspaceReceiptPartnersPage loading component[/-][+][$250] Refactor WorkspaceReceiptPartnersPage loading component[/+]melvin-bot commentedon Jan 9, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022009684263007938026
melvin-bot commentedon Jan 9, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 (
External)Eskalifer1 commentedon Jan 9, 2026
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 commentedon Jan 9, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
The
WorkspaceReceiptPartnersPagecomponent currently usesActivityIndicatorto 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
ActivityIndicatorduring the initial data load, and only displaysHeaderWithBackButton(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 improvedFullscreenLoadingIndicatorprovides 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
ActivityIndicatorwithFullscreenLoadingIndicatorand enable the back button recovery mechanism.Update the loading state rendering to use
FullscreenLoadingIndicatorwithshouldUseGoBackButton={true}here
App/src/pages/workspace/receiptPartners/WorkspaceReceiptPartnersPage.tsx
Lines 247 to 251 in 75a8599
What alternative solutions did you explore? (Optional)
N/A
PiyushChandra17 commentedon Jan 9, 2026
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.
27 remaining items
melvin-bot commentedon Jan 20, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 20, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.4-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-27. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 27, 2026
Issue is ready for payment but no BZ is assigned. @RachCHopkins you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
ikevin127 commentedon Jan 28, 2026
👋 Hi @RachCHopkins, when you get a chance - do you mind helping us with a payment summary ? Much appreciated 🙌
✅ No BZ checklist needed here as this was a refactor.
ikevin127 commentedon Jan 28, 2026
@RachCHopkins Friendly bump
RachCHopkins commentedon Jan 29, 2026
Payment Summary:
Upwork job here
RachCHopkins commentedon Jan 29, 2026
Contributor has been paid, the contract has been completed, and the Upwork post has been closed.
🟢 to @ikevin127 to request payment
garrettmknight commentedon Feb 2, 2026
$250 approved for @ikevin127