Skip to content

[HOLD for payment 2024-11-18] [$125] Expensify Card - Back button on issue card page returns to Bank account verified page #51883

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.56-3
Reproducible in staging?: Y
Reproducible in production?: N/A Unable to check
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): applausetester+kh081006@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Expensify Card
  3. Click Issue new card
  4. Add a bank account
  5. Dismiss the RHP
  6. Click Issue new account
  7. Select the added bank account
  8. On Bank account verified page, click Got it
  9. On Issue card page, click RHP back button

Expected Result:

The RHP will be dismissed

Actual Result:

App returns to Bank account verified page

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
Bug6652488_1730477794594.bandicam_2024-11-02_00-05-53-300.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @OfstadC
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021853850206557900537
  • Upwork Job ID: 1853850206557900537
  • Last Price Increase: 2024-11-05
  • Automatic offers:
    • Nodebrute | Contributor | 104755066
    • rayane-djouah | Contributor | 104792968

Activity

  1. melvin-bot commented on Nov 1, 2024

    @melvin-bot

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

  2. melvin-bot commented on Nov 1, 2024

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Nov 1, 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.
  4. Nodebrute commented on Nov 1, 2024

    @Nodebrute
    Contributor

    Proposal

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

    Back button on issue card page returns to Bank account verified page

    What is the root cause of that problem?

    When user press Got it we simply navigate to next page rather then dismissing the current modal

    onPress={() => Navigation.navigate(ROUTES.WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW.getRoute(policyID))}

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

    We should also dismiss the modal before navigating here. We can do something like this

       onPress={() => {
                                    Navigation.dismissModal();
                                    Navigation.navigate(ROUTES.WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW.getRoute(policyID)); 
                                }}
    

    It's a similar approach that we also use in other places

    What alternative solutions did you explore? (Optional)

    We can also use goBack() before navigating to WORKSPACE_EXPENSIFY_CARD_ISSUE_NEW

  5. thienlnam commented on Nov 1, 2024

    @thienlnam
    Contributor

    I'm not sure if this is actually a bug or not - adding external so we can get a BZ assigned to determine whether we should fix this or not

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 1, 2024
  7. melvin-bot commented on Nov 1, 2024

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 1, 2024
  9. melvin-bot commented on Nov 1, 2024

    @melvin-bot

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

  10. 55 remaining items

  11. changed the title [-][$125] Expensify Card - Back button on issue card page returns to Bank account verified page[/-] [+][HOLD for payment 2024-11-18] [$125] Expensify Card - Back button on issue card page returns to Bank account verified page[/+] on Nov 11, 2024
  12. melvin-bot commented on Nov 11, 2024

    @melvin-bot

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

  13. melvin-bot commented on Nov 11, 2024

    @melvin-bot

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

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

  14. melvin-bot commented on Nov 11, 2024

    @melvin-bot

    @rayane-djouah @OfstadC 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. OfstadC commented on Nov 14, 2024

    @OfstadC
    Contributor

    @rayane-djouah Please complete the BZ checklist before the payment date. Thank you! 😃

  16. rayane-d commented on Nov 15, 2024

    @rayane-d
    Contributor

    BugZero Checklist:

    • 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 a PR
      • 2z. Other:

      Who reported the bug:

      • 3a. Expensify user
      • 3b. Expensify employee
      • 3c. Contributor
      • 3d. QA
      • 3z. Other:
    • 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: https://github.com/Expensify/App/pull/51407/files#r1844661469

    • 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

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

    • @OfstadC Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    #### Precondition:
    
    - A workspace has been created.
    - The "Expensify Card" feature has been enabled on the "More features" page.
    
    #### Test:
    
    1. Go to workspace settings > Expensify Card
    2. Click Issue new card
    3. Add a bank account
    4. Dismiss the RHP
    5. Click Issue new card
    6. Select the added bank account
    7. On the "Bank account verified" page, click "Got it"
    8. On the "Issue card" page, click RHP back button
    9. Verify that the RHP is dismissed after clicking the back button.
    
    

    Do we agree 👍 or 👎

  17. OfstadC commented on Nov 18, 2024

    @OfstadC
    Contributor
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