Skip to content

[HOLD for payment 2024-12-09] [HOLD for payment 2024-12-07] Categorize it -Upgrade success view opens when navigating back from category list/confirm page #53309

Closed

Description

@IuliiaHerets

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.68-2
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+232803@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Precondition:

  • Account has no workspace.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Track a manual expense.
  4. Tap Categorize it.
  5. Tap Upgrade.
  6. Tap Got it, thanks.
  7. Tap app back button.
  8. Note that it still opens upgrade success view.
  9. Tap Got it, thanks.
  10. Select a category.
  11. Tap app back button on the confirmation page.
  12. Note that it still opens upgrade success view.
  13. Tap app back button again.
  14. Note that now only category list will open.

Expected Result:

In Step 8 and 12, upgrade success view should be removed from the navigation path once "Got it, thanks" is tapped (similar to what is done here #52091).

Actual Result:

In Step 8 and 12, upgrade success view opens when navigating back to the previous page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6679799_1732871295619.ScreenRecording_11-29-2024_17-00-20_1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 29, 2024
  2. melvin-bot commented on Nov 29, 2024

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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. melvin-bot commented on Nov 29, 2024

    @melvin-bot

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

  4. melvin-bot commented on Nov 29, 2024

    @melvin-bot

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

  5. github-actions commented on Nov 29, 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.
  6. trjExpensify commented on Nov 29, 2024

    @trjExpensify
    Contributor

    Yep, let's dismiss close the RHP if they go back, which would be consistent with other flows. For example:

    2024-11-29_11-01-46.mp4
  7. 14 remaining items

  8. melvin-bot commented on Nov 30, 2024

    @melvin-bot

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

  9. melvin-bot commented on Nov 30, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 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-12-07. 🎊

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

    • @Ollyws requires payment through NewDot Manual Requests
    • @nkdengineer requires payment (Needs manual offer from BZ)
  10. melvin-bot commented on Nov 30, 2024

    @melvin-bot

    @Ollyws @trjExpensify @Ollyws 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]

  11. changed the title [-][HOLD for payment 2024-12-07] Categorize it -Upgrade success view opens when navigating back from category list/confirm page[/-] [+][HOLD for payment 2024-12-09] [HOLD for payment 2024-12-07] Categorize it -Upgrade success view opens when navigating back from category list/confirm page[/+] on Dec 2, 2024
  12. melvin-bot commented on Dec 2, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.69-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-12-09. 🎊

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

    • @Ollyws requires payment through NewDot Manual Requests
    • @nkdengineer requires payment (Needs manual offer from BZ)
  13. melvin-bot commented on Dec 2, 2024

    @melvin-bot

    @Ollyws @trjExpensify @Ollyws 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]

  14. melvin-bot commented on Dec 9, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@trjExpensify)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. trjExpensify commented on Dec 9, 2024

    @trjExpensify
    Contributor

    This was a fix from the categorize it update PR, so I think we can handle payment there centrally for this, right?

  16. trjExpensify commented on Dec 11, 2024

    @trjExpensify
    Contributor

    Closing this out to consolidate on the OG issue linked.

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions