Skip to content

HOLD for Payment 2024-06-21] Verification page is included in the last path visited url #43325

Closed

Description

@mountiny

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:
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: @adamgrzybowski
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1717758022288149

Action Performed:

With the ideal nav framework, we are storing the last visited url for the user. This way, we can ensure user is navigated where they left off.

  1. User the abracadabra page when signing in
  2. Close the tab when on the page
  3. Open new dot in a new tab

Expected Result:

Describe what you think should've happened

User should be navigated to the main home page/ chats

Actual Result:

Describe what actually happened

User is presented with the abracadabra page but they are already signed in so no need for it

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @rushatgabhane

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 7, 2024
  2. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 7, 2024
  3. melvin-bot commented on Jun 7, 2024

    @melvin-bot

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

  4. melvin-bot commented on Jun 7, 2024

    @melvin-bot

    Triggered auto assignment to @sakluger (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.

  5. added
    ReviewingHas a PR in review
    and removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 7, 2024
  6. AndrewGable commented on Jun 11, 2024

    @AndrewGable
    Contributor

    @adamgrzybowski - Can you comment here so I can assign you?

  7. adamgrzybowski commented on Jun 12, 2024

    @adamgrzybowski
    Contributor
  8. rushatgabhane commented on Jun 16, 2024

    @rushatgabhane
    Member

    PR hit production 2 days ago - #43303 (comment)

  9. rushatgabhane commented on Jun 16, 2024

    @rushatgabhane
    Member
    1. The PR that introduced the bug has been identified. Link to the PR: N.A. was always a problem.

    2. 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: N.A.

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

    4. Determine if we should create a regression test for this bug. Yes

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

                 1. Open the verification page - https://staging.new.expensify.com/v/123/456
                 2. Open the home page - https://staging.new.expensify.com
                 3. Verify that you aren't shown the magic code verification page
      
  10. rushatgabhane commented on Jun 16, 2024

    @rushatgabhane
    Member

    @sakluger could you please attach payment summary for the payment date - June 21

  11. changed the title [-]Verification page is included in the last path visited url[/-] [+]HOLD for Payment 2024-06-21] Verification page is included in the last path visited url[/+] on Jun 17, 2024
  12. sakluger commented on Jun 17, 2024

    @sakluger
    Contributor

    Summarizing payment on this issue:

    Contributor: @adamgrzybowski - no payment due
    Contributor+: @rushatgabhane - $250 - please request on Newdot on or after June 21

  13. sakluger commented on Jun 17, 2024

    @sakluger
    Contributor

    Posted! I'm going to leave this open until the payment date.

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Jun 17, 2024
  15. JmillsExpensify commented on Jun 23, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @rushatgabhane.

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