Skip to content

[Due for payment 2025-02-27] [Due for payment 2025-02-26] App crashed when Category clicked in report search filter view #57048

Closed

Description

@m-natarajan

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.1.0-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @quinthar
Slack conversation (hyperlinked to channel name): #quality

Action Performed:

  1. Navigate to report search > Expenses
  2. Click Filters
  3. Click From
  4. Pick any user from
  5. Click the back arrow
  6. Click From again and select any user
  7. Click Save
  8. Click Category

Expected Result:

List of categories displayed to select

Actual Result:

Uh-oh, Something went wrong message displayed. (App crashed). Able to reproduce by clicking the refresh button and repeating the steps, Clicking reset filters and repeating the steps also results in app crash.

More screenshots and onyx state logs in OP

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
Recording.994.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

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

    @melvin-bot

    Triggered auto assignment to @amyevans (AutoAssignerNewDotQuality)

  3. melvin-bot commented on Feb 18, 2025

    @melvin-bot

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

  4. melvin-bot commented on Feb 18, 2025

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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. melvin-bot commented on Feb 18, 2025

    @melvin-bot

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

  6. 12 remaining items

  7. changed the title [-]App crashed when `Category` clicked in report search filter view[/-] [+][Due for payment 2025-02-26] App crashed when `Category` clicked in report search filter view[/+] on Feb 19, 2025
  8. melvin-bot commented on Feb 19, 2025

    @melvin-bot

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

  9. melvin-bot commented on Feb 19, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.0-2 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 2025-02-26. 🎊

  10. melvin-bot commented on Feb 19, 2025

    @melvin-bot

    @francoisl / @amyevans @stephanieelliott @francoisl / @amyevans 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 [-][Due for payment 2025-02-26] App crashed when `Category` clicked in report search filter view[/-] [+][Due for payment 2025-02-27] [Due for payment 2025-02-26] App crashed when `Category` clicked in report search filter view[/+] on Feb 20, 2025
  12. melvin-bot commented on Feb 20, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.1-6 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 2025-02-27. 🎊

  13. melvin-bot commented on Feb 20, 2025

    @melvin-bot

    @francoisl / @amyevans @stephanieelliott @francoisl / @amyevans 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. amyevans commented on Feb 21, 2025

    @amyevans
    Contributor

    This was fixed internally so no payouts due, I think we're fine to close!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

AutoAssignerNewDotQualityUsed to assign quality issues to engineersAwaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions