Skip to content

Report - App crashes when trying to open unloaded paid distance expenses #52889

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.65-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5250645
Email or phone of affected tester (no customers): sustinov@applausemail.com
Issue reported by: Applause Internal Team

Action Performed:

Prerequisites:
Create a WS, invite an employee

Steps:

  1. Open New Expensify app Hybrid
  2. Under the employee account, send 2 or more distance charges to the WS room
  3. Under the administrator account, pay the distance charges received from the employee
  4. Re-login to the application under the employee account
  5. Go to the WS room
  6. Open paid distance expenses

Expected Result:

App should not crash when trying to open unloaded paid distance expenses

Actual Result:

App crashes when trying to open unloaded paid distance expenses

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

2111_3.txt

Bug6671687_1732181872118.Recording__233.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @carlosmiceli

Activity

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

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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 21, 2024

    @melvin-bot

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

  4. melvin-bot commented on Nov 21, 2024

    @melvin-bot

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

  5. github-actions commented on Nov 21, 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. IuliiaHerets commented on Nov 21, 2024

    @IuliiaHerets
    Author

    Same problem happens with the thread. Do we need to log a new issue for it?

    Recording.234.mp4
  7. Krishna2323 commented on Nov 21, 2024

    @Krishna2323
    Contributor

    Same problem happens with the thread. Do we need to log a new issue for it?

    @carlosmiceli @IuliiaHerets this issue along with the thread issue will be fixed once this PR is merged. I don't think we need to create new issue.

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 21, 2024
  9. carlosmiceli commented on Nov 21, 2024

    @carlosmiceli
    Contributor

    @Krishna2323 Understood! @IuliiaHerets seems that the PR is already merged, can we check if the issue is indeed gone?

  10. melvin-bot commented on Nov 25, 2024

    @melvin-bot

    @carlosmiceli, @RachCHopkins Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. carlosmiceli commented on Nov 25, 2024

    @carlosmiceli
    Contributor

    Not opverdue.

  12. carlosmiceli commented on Nov 28, 2024

    @carlosmiceli
    Contributor

    since this is merged in prod, seems like we can close this: #52889 (comment)

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions