Skip to content

[HOLD for payment 2024-05-08] [$250] Profile - Display name is not updating in "Share Somewhere" section #39607

Closed

Description

@kbecciv

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: v1.4.60-1
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to Profile.
  2. Add or change the Display name.
  3. Use FAB to assign a task.
  4. Add a title and click "Next" to share somewhere.
  5. Notice that the Display name isn't updated for the account email (email signed in).

Expected Result:

When the Display name is changed, it should be updated in the "Share Somewhere" section for the account email (email signed in).

Actual Result:

Display name is not updating in "Share Somewhere" section

Workaround:

n/a

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

Add any screenshot/video evidence

Bug6437941_1712234508566.Screen_Recording_2024-04-04_at_1.14.37_AM.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0109207e4c67cd7686
  • Upwork Job ID: 1776016111925432320
  • Last Price Increase: 2024-04-11
  • Automatic offers:
    • hungvu193 | Reviewer | 0
    • nkdengineer | Contributor | 0
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. melvin-bot commented on Apr 4, 2024

    @melvin-bot

    Triggered auto assignment to @bondydaa (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. github-actions commented on Apr 4, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  3. kbecciv commented on Apr 4, 2024

    @kbecciv
    Author

    We think that this bug might be related to #vip-vsb

  4. bondydaa commented on Apr 4, 2024

    @bondydaa
    Contributor

    I'm looking into this, nothing in the checklist stands out to me that might be something that broke this so having to dive into the code and see what exactly gets called.

  5. bondydaa commented on Apr 4, 2024

    @bondydaa
    Contributor

    okay i don't think it's a problem with the API, i see the response coming back properly with the updated data
    image

    And I see in the onyx db that it's been updated there
    image

    So this makes me think that for some reason the Share Somewhere component isn't properly subscribing to the onyx data or something so going to take a closer look at that.

  6. bondydaa commented on Apr 4, 2024

    @bondydaa
    Contributor

    Hmm this PR is sus to me after looking at the components involved here: #38207

  7. bondydaa commented on Apr 4, 2024

    @bondydaa
    Contributor

    okay yes I believe I've confirmed this by testing locally.

    checking out 1.4.60-1 locally I see the same behavior and then reverting it I can't reproduce it anymore.

    cc @grgia @hungvu193 @TMisiukiewicz can you take a look here?

  8. bondydaa commented on Apr 4, 2024

    @bondydaa
    Contributor

    I guess what we need is a way to invalidate the option list cache when personal details are updated, if there is a way to do that in the PR can you let me know?

    or if that's still to come then maybe we consider this not a blocker?

    makes me think of my favorite tweet 😂 https://twitter.com/codinghorror/status/506010907021828096

  9. jasperhuangg commented on Apr 4, 2024

    @jasperhuangg
    Contributor

    @bondydaa This seems like a pretty minor bug–and since we've already narrowed down which PR it's coming from I think we can just mark it NAB and have @TMisiukiewicz look into a fix

  10. 52 remaining items

  11. changed the title [-][$250] Profile - Display name is not updating in "Share Somewhere" section[/-] [+][HOLD for payment 2024-05-08] [$250] Profile - Display name is not updating in "Share Somewhere" section[/+] on May 1, 2024
  12. melvin-bot commented on May 1, 2024

    @melvin-bot

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

  13. melvin-bot commented on May 1, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.68-3 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-05-08. 🎊

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

  14. melvin-bot commented on May 1, 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:

    • [@hungvu193] The PR that introduced the bug has been identified. Link to the PR:
    • [@hungvu193] 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:
    • [@hungvu193] 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:
    • [@hungvu193] Determine if we should create a regression test for this bug.
    • [@hungvu193] 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.
    • [@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  15. hungvu193 commented on May 1, 2024

    @hungvu193
    Contributor
    • The PR that introduced the bug has been identified. Link to the PR: perf: Cache search options #38207
    • 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:
    • 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: N/A
    • Determine if we should create a regression test for this bug: No

    This is new feature, we can treat it as a follow up of #38207

  16. melvin-bot commented on May 13, 2024

    @melvin-bot

    @JmillsExpensify, @bondydaa, @hungvu193, @nkdengineer Huh... This is 4 days overdue. Who can take care of this?

  17. hungvu193 commented on May 14, 2024

    @hungvu193
    Contributor

    Bump @JmillsExpensify for payment here

  18. JmillsExpensify commented on May 14, 2024

    @JmillsExpensify
    Contributor

    Payment summary:

  19. JmillsExpensify commented on May 14, 2024

    @JmillsExpensify
    Contributor

    Both Contributor contracts paid out via Upwork, so I'm closing this issue.

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions