Skip to content

[HOLD for payment 2024-03-14] [HOLD for payment 2024-03-13] [$500] Distance - Request details page loads infinitely when the request is created offline #37743

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.47-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go offline.
  3. Go to workspace chat.
  4. Create a distance request.
  5. Go to the distance request details page.

Expected Result:

User will be able to access request details page even though the request is created offline.

Actual Result:

The request details page loads infinitely when the request is created offline.

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

Bug6402548_1709630058066.20240305_120325.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01dfe56b23d3d01ac3
  • Upwork Job ID: 1765255088135561216
  • Last Price Increase: 2024-03-06
Issue OwnerCurrent Issue Owner: @joekaufmanexpensify

Activity

  1. github-actions commented on Mar 5, 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.
  2. melvin-bot commented on Mar 5, 2024

    @melvin-bot

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

  3. kbecciv commented on Mar 5, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave5-free-submitters
    CC @dylanexpensify

  4. paultsimura commented on Mar 5, 2024

    @paultsimura
    Contributor

    It's being fixed in #37232

  5. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  6. melvin-bot commented on Mar 6, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  7. 36 remaining items

  8. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.48-0 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-03-14. 🎊

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

    • @paultsimura requires payment (Needs manual offer from BZ)
  9. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  10. joekaufmanexpensify commented on Mar 11, 2024

    @joekaufmanexpensify
    Contributor

    @paultsimura could you please handle your portion of the BZ checklist so we can prep to issue payment?

  11. paultsimura commented on Mar 11, 2024

    @paultsimura
    Contributor

    Regression Test Proposal

    1. Go offline.
    2. Go to a workspace chat.
    3. Create a new distance request.
    4. Open the distance request details page (i.e. transaction thread).
    5. Verify the request details page loads successfully even though the request was created offline.

    Do we agree 👍 or 👎

  12. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    TY! No additional regression test is needed here. This is already captured in the existing test: Request Money - Distance Expense - Create distance Expense (Offline)

  13. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    All set to issue payment. We only need to pay @paultsimura $500 for C+ review via upwork.

  14. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    @paultsimura offer sent for $500!

  15. paultsimura commented on Mar 13, 2024

    @paultsimura
    Contributor

    Thanks, accepted😌

  16. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    TY!

  17. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    $500 sent and contract ended

  18. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    Upwork job closed.

  19. joekaufmanexpensify commented on Mar 13, 2024

    @joekaufmanexpensify
    Contributor

    Good to go here. Thanks everyone!

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