Skip to content

Can't set distance rate on a new workspace, Oops... something went wrong error appears #39341

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: 1.4.58-2
Reproducible in staging?: y
Reproducible in production?: n
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):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:

Action Performed:

  1. Log in with a new expensifail account
  2. Create a new workspace
  3. Enable distance rates in the More features tab
  4. Navigate to Distance rates
  5. Tap on the distance rate
  6. Tap on the rate
  7. Change the rate and save it

Expected Result:

I should be able to set a new rate without errors.

Actual Result:

I can't set distance rate on a new workspace, "Oops... something went wrong" error appears when I try. Sometimes I get a Hmm... it's not here" error when trying to open the rate.

Workaround:

unknown

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

Bug6433518_1711916659493.NIUY9524.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. melvin-bot commented on Mar 31, 2024

    @melvin-bot

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

  4. github-actions commented on Mar 31, 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.
  5. joekaufmanexpensify commented on Apr 1, 2024

    @joekaufmanexpensify
    Contributor

    @deetergp do you think this should be a deploy blocker? I can reproduce

  6. tgolen commented on Apr 1, 2024

    @tgolen
    Contributor

    I think it should, yes. This is related to the new collect workspaces being created. I'm guessing the backend is throwing an error. Can someone please get the requestID of the failed API call or at least post the login of the account you used to reproduce the issue?

  7. assigned and unassigned on Apr 1, 2024
  8. joekaufmanexpensify commented on Apr 1, 2024

    @joekaufmanexpensify
    Contributor

    Yep, one sec!

  9. joekaufmanexpensify commented on Apr 1, 2024

    @joekaufmanexpensify
    Contributor

    The account I used earlier today was jkaufman+18@expensifail.com. However, I'm trying to get a requestID for a new attempt and I can't reproduce this now on staging any longer. @tgolen are you still able to reproduce it?

  10. tgolen commented on Apr 1, 2024

    @tgolen
    Contributor

    I wasn't able to reproduce it. You can see here that I changed the default rate to 0.672 as well as add a new rate:

    image

  11. joekaufmanexpensify commented on Apr 1, 2024

    @joekaufmanexpensify
    Contributor

    Cool. Yeah it worked for me on two different accounts just now too.

  12. tgolen commented on Apr 1, 2024

    @tgolen
    Contributor

    I guess since neither of us can reproduce it, I'll close this for now. Thank you, Joe!

  13. joekaufmanexpensify commented on Apr 1, 2024

    @joekaufmanexpensify
    Contributor

    Course!

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions