search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.57k stars 2.91k forks source link

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

Open IuliiaHerets opened 23 hours ago

IuliiaHerets commented 23 hours ago

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:

Screenshots/Videos

2111_3.txt

https://github.com/user-attachments/assets/1ffe302f-a556-4b3b-b5e2-ef9ea5780b06

View all open jobs on GitHub

melvin-bot[bot] commented 23 hours ago

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.

melvin-bot[bot] commented 23 hours ago

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

melvin-bot[bot] commented 23 hours ago

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

github-actions[bot] commented 23 hours ago

:wave: 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.
IuliiaHerets commented 23 hours ago

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

https://github.com/user-attachments/assets/70a21759-9fe9-4387-b00d-7b7f445b0655

Krishna2323 commented 22 hours ago

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.

carlosmiceli commented 20 hours ago

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