Skip to content

[HOLD for #29428] - [$500] Login - Settings page has no skeleton placeholder when the page is loading #30362

Closed

Description

@lanitochka17

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


Version Number: 1.3.90-2

Reproducible in staging?: Yes

Reproducible in production?: Yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

Action Performed:

  1. Launch New Expensify app
  2. Log in with a high traffic account
  3. When the page is loading, open Settings

Expected Result:

Settings page has skeleton placeholder when the page is loading

Actual Result:

Settings page has no skeleton placeholder when the page is loading

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

Android: Native
Android: mWeb Chrome
iOS: Native
Bug6250476_1698249216544.RPReplay_Final1698199526.mp4
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01fc78993cd9ce2750
  • Upwork Job ID: 1717214985723400192
  • Last Price Increase: 2023-10-25
  • Automatic offers:
    • bernhardoj | Contributor | 27699378

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 25, 2023
  2. changed the title [-]Login - Settings page has no skeleton placeholder when the page is loading[/-] [+][$500] Login - Settings page has no skeleton placeholder when the page is loading[/+] on Oct 25, 2023
  3. melvin-bot commented on Oct 25, 2023

    @melvin-bot
  4. melvin-bot commented on Oct 25, 2023

    @melvin-bot

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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 25, 2023
  6. melvin-bot commented on Oct 25, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  7. melvin-bot commented on Oct 25, 2023

    @melvin-bot

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

  8. bernhardoj commented on Oct 25, 2023

    @bernhardoj
    Contributor

    Proposal

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

    There is no skeleton when opening the settings page after login.

    What is the root cause of that problem?

    Previously, we will show the skeleton if the user's personal details data is empty.

    {_.isEmpty(props.currentUserPersonalDetails) || _.isUndefined(props.currentUserPersonalDetails.displayName) ? (
    <CurrentUserPersonalDetailsSkeletonView
    backgroundColor={themeColors.appBG}
    avatarSize={CONST.AVATAR_SIZE.XLARGE}
    />
    ) : (

    However, in this functional migration PR, if the personal detail is empty, we return null.

    // On the very first sign in or after clearing storage these
    // details will not be present on the first render so we'll just
    // return nothing for now.
    if (_.isEmpty(props.currentUserPersonalDetails)) {
    return null;
    }

    Also, the skeleton color is currently the same color as the RHP background color (#061B09), so we still won't be able to see the skeleton.

    <CurrentUserPersonalDetailsSkeletonView
    backgroundColor={themeColors.appBG}

    Here is the reason why it's changed. But now, the settings header section background color is back to the app bg color.

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

    Remove these codes:

    if (_.isEmpty(props.currentUserPersonalDetails)) {
    return null;
    }

    backgroundColor={themeColors.appBG}

    Screen.Recording.2023-10-26.at.00.53.28.mov
  9. ishpaul777 commented on Oct 25, 2023

    @ishpaul777
    Contributor

    I beleive this will be resolved in this PR

    cc @robertKozik

  10. robertKozik commented on Oct 26, 2023

    @robertKozik
    Contributor

    Yeah I confirm, it should be resolved by the linked PR. Maybe we can put this issue on hod until the PR will be merged? After that we can retest this scenario to be sure it's fixed

  11. bernhardoj commented on Oct 27, 2023

    @bernhardoj
    Contributor

    I think that PR would partly resolve the issue, but I agree we can hold for it.

  12. 19 remaining items

  13. bernhardoj commented on Nov 16, 2023

    @bernhardoj
    Contributor

    PR is ready

    cc: @thesahindia

  14. CortneyOfstad commented on Dec 6, 2023

    @CortneyOfstad
    Contributor

    @thesahindia any update on the PR above? Thanks!

  15. thesahindia commented on Dec 10, 2023

    @thesahindia
    Member

    @CortneyOfstad, the PR was merged 3 weeks ago.

  16. bernhardoj commented on Dec 16, 2023

    @bernhardoj
    Contributor

    I think this is ready for payment

  17. CortneyOfstad commented on Dec 21, 2023

    @CortneyOfstad
    Contributor

    Sorry for missing this! @thesahindia in the future, please make sure to remove the "Reviewing" label and add the "awaiting payment" labels, as this will trigger the payment process to begin 👍

  18. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Dec 21, 2023
  19. situchan commented on Dec 21, 2023

    @situchan
    Contributor

    Sorry for missing this! @thesahindia in the future, please make sure to remove the "Reviewing" label and add the "awaiting payment" labels, as this will trigger the payment process to begin 👍

    FYI: C+ team doesn't have permission to add/remove labels. It should be done by BZ or engineer

  20. CortneyOfstad commented on Dec 21, 2023

    @CortneyOfstad
    Contributor

    Weird, I was under the impression they could — odd. But thanks for the heads up!

    @bernhardoj I've sent you an offer in Upwork as the previous one expired. Please let me know as soon as that is accepted and I can get that paid to you ASAP 👍

  21. bernhardoj commented on Dec 21, 2023

    @bernhardoj
    Contributor

    @CortneyOfstad accepted. Thanks!

  22. CortneyOfstad commented on Dec 21, 2023

    @CortneyOfstad
    Contributor

    Payment Summary

    @thesahindia to be paid $500 via NewDot
    @bernhardoj was paid $500 via Upwork

  23. JmillsExpensify commented on Jan 14, 2024

    @JmillsExpensify
    Contributor

    $500 payment approved for @thesahindia based on comment above.

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions