Skip to content

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

Closed

Description

@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 OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @RachCHopkins

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jan 9, 2026
  2. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 9, 2026
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 9, 2026
  4. changed the title [-]Refactor WorkspaceReceiptPartnersPage loading component[/-] [+][$250] Refactor WorkspaceReceiptPartnersPage loading component[/+] on Jan 9, 2026
  5. melvin-bot commented on Jan 9, 2026

    @melvin-bot
  6. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 9, 2026
  7. melvin-bot commented on Jan 9, 2026

    @melvin-bot

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

  8. Eskalifer1 commented on Jan 9, 2026

    @Eskalifer1
    Contributor

    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

  9. samranahm commented on Jan 9, 2026

    @samranahm
    Contributor

    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

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

    What alternative solutions did you explore? (Optional)

    N/A

  10. PiyushChandra17 commented on Jan 9, 2026

    @PiyushChandra17
    Contributor

    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.

  11. 27 remaining items

  12. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    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:

  14. melvin-bot commented on Jan 27, 2026

    @melvin-bot

    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!

  15. ikevin127 commented on Jan 28, 2026

    @ikevin127
    Contributor

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

  16. ikevin127 commented on Jan 28, 2026

    @ikevin127
    Contributor

    @RachCHopkins Friendly bump

  17. RachCHopkins commented on Jan 29, 2026

    @RachCHopkins
    Contributor

    Payment Summary:

    Upwork job here

  18. RachCHopkins commented on Jan 29, 2026

    @RachCHopkins
    Contributor

    Contributor has been paid, the contract has been completed, and the Upwork post has been closed.

    🟢 to @ikevin127 to request payment

  19. garrettmknight commented on Feb 2, 2026

    @garrettmknight
    Contributor

    $250 approved for @ikevin127

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorTask

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions