Skip to content

[$250] Track Expense - Hmm..not here page on selecting category with no existing workspace #43073

Closed

Description

@kbecciv

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: 1.4-79-3
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4594444&group_by=cases:section_id&group_order=asc&group_id=309130
Issue reported by: Applause - Internal Team

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Create new account
  3. Submit a track expense in the self DM
  4. Click on Categorize it on the actionable whisper options of a track expense
  5. Select a category shown in the list to categorize the expense

Expected Result:

As per step TC 6 - After selecting a category, the "To" field should be filled with a "new" workspace

Actual Result:

Hmm..not here page on selecting category with no existing workspace

Workaround:

n/a

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

image

image

Bug6502071_1717534334395.RPReplay_Final1717534228.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01a18541e1775fab5a
  • Upwork Job ID: 1798437262634635540
  • Last Price Increase: 2024-06-05
Issue OwnerCurrent Issue Owner: @mananjadhav

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jun 4, 2024
  2. melvin-bot commented on Jun 4, 2024

    @melvin-bot

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

  3. github-actions commented on Jun 4, 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. kbecciv commented on Jun 4, 2024

    @kbecciv
    Author

    We think that this bug might be related to #vip-vsb

  5. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    Looking into this.

  6. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    Reproduced it locally. I think this PR is really suspicious given the timing and the area of the codebase. Reverting that PR locally doesn't fix it though, so that doesn't seem like its the root cause.

    Not 100% sure if this is backend or frontend, seems like frontend because I can't find any wonky network requests or logs that are giving me any leads. Though maybe it has to do with bad handling of onyx updates in the backend. Not sure.

    Reached out in #expensify-opensource (link)

  7. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    I think this might be backend related, since I went back about a week and a half in App history and its still an issue. Stuck on how to debug this. Can't seem to figure out where it is going wrong.

  8. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    Huh, well when I actually try to reproduce this on staging it doesn't reproduce, so maybe someone put out a fix that is related to this.

  9. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    Weird, yup, pulled everything and now its working locally on main.

  10. blimpich commented on Jun 4, 2024

    @blimpich
    Contributor

    Asked QA to retest

    In the meantime I think we can demote as this is no longer reproducing for me on staging or locally. Should probably figure out what the exact cause was, but seems to be fixed.

  11. removed
    DeployBlockerIndicates it should block deploying the API
    on Jun 4, 2024
  12. 24 remaining items

  13. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 10, 2024
  14. mananjadhav commented on Jun 11, 2024

    @mananjadhav
    Collaborator

    Reviewing proposals.

  15. mananjadhav commented on Jun 13, 2024

    @mananjadhav
    Collaborator

    I am testing the proposals to see if it works and doesn't break anything. I'll have an update before EOD today.

  16. CortneyOfstad commented on Jun 17, 2024

    @CortneyOfstad
    Contributor

    @mananjadhav any update on the testing?

  17. melvin-bot commented on Jun 17, 2024

    @melvin-bot

    @mananjadhav, @CortneyOfstad, @blimpich Whoops! This issue is 2 days overdue. Let's get this updated quick!

  18. melvin-bot commented on Jun 18, 2024

    @melvin-bot

    @mananjadhav @CortneyOfstad @blimpich this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  19. mananjadhav commented on Jun 19, 2024

    @mananjadhav
    Collaborator

    I was out sick past 3-4 days. I'll post an update today/tomorrow.

  20. CortneyOfstad commented on Jun 19, 2024

    @CortneyOfstad
    Contributor

    Thanks @mananjadhav and hope you're feeling better!

  21. mananjadhav commented on Jun 23, 2024

    @mananjadhav
    Collaborator

    Apologies for the delay here. I've been trying to reproduce this on staging and the latest main. But I haven't been able to reproduce the bug. Earlier when it was reported I was able to, but not recently. @kbecciv @CortneyOfstad @blimpich Are you able to consistently reproduce this?

    Here's the video from Web

    web-not-found-on-categorize.mov

    iPhone Safari

    mweb-safari-not-found-on-categorize.mp4

    and I've tried this on Native, Mobile Web, Mac Safari. Tried it with 3 different new accounts.

    @CortneyOfstad @blimpich I do see Not found when we click on the Workspace name. I am assuming that is expected as the workspace is not created yet. May be that shouldn't be clickable? But definitely a separate issue.

  22. blimpich commented on Jun 24, 2024

    @blimpich
    Contributor

    I can no longer reproduce this either, seems to have been fixed elsewhere. Closing.

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

Metadata

Metadata

Labels

BugSomething 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