Skip to content

[HOLD for payment 2024-11-28] [$250] Contact Methods - Navigated back to "New contact method" when going back to online #51189

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: 9.0.51-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): dave0123seife@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to account settings > Profile
  2. Click on "Contact Method"
  3. Click on "New Contact method"
  4. Add a email > Add
  5. In the verification page go Offline and return back online

Expected Result:

User is not Navigated back to "New contact method" when going back to online

Actual Result:

Navigated back to "New contact method" when going back to online

Workaround:

Unknown

Platforms:

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

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6641216_1729527065628.Screen_Recording_2024-10-21_at_6.57.57_in_the_evening.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021853397434469388025
  • Upwork Job ID: 1853397434469388025
  • Last Price Increase: 2024-11-11
  • Automatic offers:
    • wildan-m | Contributor | 104874938
Issue OwnerCurrent Issue Owner: @zanyrenney

Activity

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

    @melvin-bot

    Triggered auto assignment to @zanyrenney (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. lanitochka17 commented on Oct 21, 2024

    @lanitochka17
    Author

    @zanyrenney FYI 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. ChavdaSachin commented on Oct 21, 2024

    @ChavdaSachin
    Contributor

    No more reproducible, it was solved here
    #49445

  5. zanyrenney commented on Oct 23, 2024

    @zanyrenney
    Contributor

    Closing as solved above!

  6. lanitochka17 commented on Oct 29, 2024

    @lanitochka17
    Author

    Issue is still reproducible on the mWeb/Chrome on the latest build 9.0.55-2

    Record_2024-10-29-14-44-02.mp4
  7. zanyrenney commented on Oct 29, 2024

    @zanyrenney
    Contributor

    Hmm i can't reproduce this.

  8. zanyrenney commented on Oct 31, 2024

    @zanyrenney
    Contributor

    @lanitochka17 still about to reproduce?

  9. lanitochka17 commented on Oct 31, 2024

    @lanitochka17
    Author

    User is still Navigated back to "New contact method". But now tester is seeing that user is navigated to "New contact method" page when pressing on cmd + D.

    Screen.Recording.2024-10-31.at.5.53.19.in.the.afternoon.mp4
  10. 33 remaining items

  11. changed the title [-][$250] Contact Methods - Navigated back to "New contact method" when going back to online[/-] [+][HOLD for payment 2024-11-28] [$250] Contact Methods - Navigated back to "New contact method" when going back to online[/+] on Nov 21, 2024
  12. melvin-bot commented on Nov 21, 2024

    @melvin-bot

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

  13. melvin-bot commented on Nov 21, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.64-4 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-11-28. 🎊

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

  14. melvin-bot commented on Nov 21, 2024

    @melvin-bot

    @fedirjh @zanyrenney @fedirjh The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. zanyrenney commented on Nov 28, 2024

    @zanyrenney
    Contributor

    I have asked @fedirjh to complete checklist

  16. fedirjh commented on Nov 28, 2024

    @fedirjh
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: Show No access Modal when Copilot tries to add new contact method on behalf of owner. #50643 (comment)

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    • N/A

    Test:

    1. Navigate to Account Settings → Profile
    2. Click on "Contact Method"
    3. Click on "New Contact method"
    4. Add an email → Add
    5. On the verification page, go Offline and return Online
    6. Verify User is not Navigated back to "New contact method" when going back to online

    Do we agree 👍 or 👎

  17. zanyrenney commented on Nov 28, 2024

    @zanyrenney
    Contributor

    payment summary

    @wildan-m requires payment automatic offer (Contributor) - paid $250 via upwork
    @fedirjh requires payment through NewDot Manual Requests - please request $250 via ND.

  18. garrettmknight commented on Dec 10, 2024

    @garrettmknight
    Contributor

    $250 approved for @fedirjh

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