Skip to content

[HOLD for payment 2024-04-05] [$125] Workspace - Categories load without loading spinner #37904

Closed

Description

@izarutskaya

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Found when validating PR : #37457

Version Number: v1.4.48-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers): applausetester+ihchat4_2902_c@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Pre-requisite: an admin account with a policyExpenseChat enabled Collect policy and another workspace.

  1. Open the app
  2. Login with admin account with Collect policy
  3. Navigate to Workspace > Settings and select the collect policy.
  4. Select the Categories page
  5. Verify that you see the loading spinner

Expected Result:

Categories load with loading spinner

Actual Result:

Categories load without loading spinner

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

2024-03-07.16.27.56.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01197fc8d66a9362f0
  • Upwork Job ID: 1770919042911531008
  • Last Price Increase: 2024-03-21
  • Automatic offers:
    • DylanDylann | Reviewer | 0
    • GandalfGwaihir | Contributor | 0

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 7, 2024
  2. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. izarutskaya commented on Mar 7, 2024

    @izarutskaya
    Author

    @alexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  4. izarutskaya commented on Mar 7, 2024

    @izarutskaya
    Author

    We think that this bug might be related to #wave8-collect-admins
    CC @zanyrenney

  5. neonbhai commented on Mar 7, 2024

    @neonbhai
    Contributor

    Proposal

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

    Categories load without loading spinner

    What is the root cause of that problem?

    We have loading spinner logic on the page, but we only check if the policyCategories are undefined, but these can be null, before fetching. Since isLoading isn't true when it is null. No loading spinner is shown

    {isLoading && (
    <ActivityIndicator
    size={CONST.ACTIVITY_INDICATOR_SIZE.LARGE}
    style={[styles.flex1]}
    color={theme.spinner}
    />
    )}

    const isLoading = !isOffline && policyCategories === undefined;

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

    We should add a check for if policyCategories are null here

    const isLoading = !isOffline && policyCategories === undefined;

  6. allgandalf commented on Mar 8, 2024

    @allgandalf
    Contributor

    Proposal

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

    Categories load without loading spinner

    What is the root cause of that problem?

    We have !isLoading set for the state where the categories are empty:

    {categoryList.length === 0 && !isLoading && (
    <WorkspaceEmptyStateSection

    But we don't have a !isLoading state for when we list of categories:

    {categoryList.length > 0 && (
    <SelectionList

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

    We need to add a !isLoading parameter to the list:

    {categoryList.length > 0 && !isLoading && (
                            <SelectionList

    What alternative solutions did you explore? (Optional)

    N/A

  7. alexpensify commented on Mar 8, 2024

    @alexpensify
    Contributor

    I'll test early next week and we can figure out the next steps. Thanks!

  8. melvin-bot commented on Mar 11, 2024

    @melvin-bot

    @alexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  9. alexpensify commented on Mar 11, 2024

    @alexpensify
    Contributor

    No update yet, I need to test.

  10. allgandalf commented on Mar 12, 2024

    @allgandalf
    Contributor

    bump @alexpensify for review

  11. alexpensify commented on Mar 13, 2024

    @alexpensify
    Contributor

    I've started a discussion in the wave room related to Collect - https://expensify.slack.com/archives/C036QM0SLJK/p1710357619580229. I should have an update by tomorrow.

  12. 39 remaining items

  13. allgandalf commented on Mar 22, 2024

    @allgandalf
    Contributor

    PR ready for review @luacmartins @DylanDylann

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 29, 2024
  15. changed the title [-][$125] Workspace - Categories load without loading spinner[/-] [+][HOLD for payment 2024-04-05] [$125] Workspace - Categories load without loading spinner[/+] on Mar 29, 2024
  16. melvin-bot commented on Mar 29, 2024

    @melvin-bot

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

  17. melvin-bot commented on Mar 29, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.57-5 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 2024-04-05. 🎊

    For reference, here are some details about the assignees on this issue:

  18. melvin-bot commented on Mar 29, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@DylanDylann] The PR that introduced the bug has been identified. Link to the PR:
    • [@DylanDylann] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@DylanDylann] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@DylanDylann] Determine if we should create a regression test for this bug.
    • [@DylanDylann] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  19. alexpensify commented on Apr 4, 2024

    @alexpensify
    Contributor

    I confirmed the job link works here. I'll complete the payment process tomorrow.

    https://www.upwork.com/jobs/~01197fc8d66a9362f0

  20. alexpensify commented on Apr 5, 2024

    @alexpensify
    Contributor

    Payouts due: 2024-04-05

    • Contributor: $125 @GandalfGwaihir
    • Contributor+: $125 @DylanDylann

    Upwork job is here.


    Closing - Everyone has been paid here

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 productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions