Skip to content

[HOLD for payment 2024-03-13] [$500] mWeb - Welcome to Expensify is shown for existing user after logging in from public room #35531

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.4.34-0
Reproducible in staging?: Y
Reproducible in production?: Y
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. Log out of New Expensify
  2. Navigate to this link - https://staging.new.expensify.com/r/5408450846930023
  3. Click on Sign In
  4. Login in with an existing account

Expected Result:

Public room chat history should be displayed.
Welcome to Expensify message should be either shown before logging in or not at all for existing users

Actual Result:

Welcome to Expensify screen is shown after log in, user is forced to close it to view public room chat history

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

Add any screenshot/video evidence

Bug6362919_1706736644415.Record_2024-01-31-20-50-10.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01adefc3ca63c114f2
  • Upwork Job ID: 1752868613105299456
  • Last Price Increase: 2024-02-15
  • Automatic offers:
    • situchan | Contributor | 0

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 1, 2024
  2. changed the title [-]mWeb - Welcome to Expensify is shown for existing user after logging in from public room[/-] [+][$500] mWeb - Welcome to Expensify is shown for existing user after logging in from public room[/+] on Feb 1, 2024
  3. melvin-bot commented on Feb 1, 2024

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 1, 2024
  5. melvin-bot commented on Feb 1, 2024

    @melvin-bot

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

  6. melvin-bot commented on Feb 1, 2024

    @melvin-bot

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

  7. lanitochka17 commented on Feb 1, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #vip-vsp
    CC @quinthar

  8. aswin-s commented on Feb 1, 2024

    @aswin-s
    Contributor

    Proposal

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

    Engagement modal is shown while visiting a public room via deep link as an anonymous user.

    What is the root cause of that problem?

    The check for showing engagement model is performed inside BottomTabBar in a useEffect.

    Welcome.show(routes, () => Navigation.navigate(ROUTES.ONBOARD));

    Inside Welcome.show method, the engamement modal is shown if current user is isFirstTimeNewExpensifyUser.

    if (!isFirstTimeNewExpensifyUser) {
    return;
    }

    if (!Policy.isAdminOfFreePolicy(allPolicies ?? undefined) && !isExitingToWorkspaceRoute && !hasSelectedChoice && !hasDismissedModal && Object.keys(allPolicies ?? {}).length === 1) {
    showEngagementModal();
    }

    However the above check doesn't consider whether the current user is an anonymous user. That's why the engagement modal gets shown for anonymous user.

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

    Check if current user is an anonymous user before showing engagement modal.

    // Add check for anonymous user
    if (!Session.isAnonymousUser() && !Policy.isAdminOfFreePolicy(allPolicies ?? undefined) && !isExitingToWorkspaceRoute && !hasSelectedChoice && !hasDismissedModal && Object.keys(allPolicies ?? {}).length === 1) {
      showEngagementModal();
    }

    What alternative solutions did you explore? (Optional)

    None

  9. sakluger commented on Feb 6, 2024

    @sakluger
    Contributor

    I asked in #vip-vsb if this is a bug or expected behavior: https://expensify.slack.com/archives/C066HJM2CAZ/p1707178252015419

  10. 48 remaining items

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 4, 2024
  12. changed the title [-][$500] mWeb - Welcome to Expensify is shown for existing user after logging in from public room[/-] [+][HOLD for payment 2024-03-13] [$500] mWeb - Welcome to Expensify is shown for existing user after logging in from public room[/+] on Mar 6, 2024
  13. melvin-bot commented on Mar 6, 2024

    @melvin-bot

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

  14. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.47-10 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-03-13. 🎊

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

  15. melvin-bot commented on Mar 6, 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:

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

    @sakluger
    Contributor

    Summarizing payment on this issue:

    Contributor: @aswin-s $500, sent offer via Upwork (https://www.upwork.com/nx/wm/offer/101367608/)
    Contributor+: @situchan $500, paid via Upwork

    @situchan could you please complete the BZ checklist?

  17. situchan commented on Mar 13, 2024

    @situchan
    Contributor

    This was missing test case from new feature of engagement modal. Not regression.

    Regression Test Proposal

    1. Logout if already logged in
    2. Navigate to this link - https://staging.new.expensify.com/r/5408450846930023
    3. Wait for the page to load completely
    4. Verify that engagement modal is not shown for anonymous user
    5. Login in with an existing account
    6. Wait for the page to load completely
    7. Verify that engagement modal is not shown
  18. sakluger commented on Mar 14, 2024

    @sakluger
    Contributor

    Thanks! I paid out all the offers and created the regression test 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.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions