Skip to content

[HOLD for payment 2024-07-17][$250] Expense - App crashes when opening an expense report after submitting another expense #44960

@lanitochka17

Description

@lanitochka17

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.5-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
Issue reported by: Applause - Internal Team

Action Performed:

  1. Sign in to an account
  2. Go to FAB > submit expense > Manual expense
  3. Enter an amount
  4. Select a user you have never submitted an expense to
  5. Submit the expense
  6. Navigate to the chat with the user you just submitted the expense to
  7. Click on the "+" icon
  8. Click on submit expense > Manual expense > Enter amount >Next > Submit
  9. Go to the combined expense report and open the first expense you submitted

Expected Result:

The expense report opens and the app does not crash

Actual Result:

App crashes after opening the report

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

Bug6535811_1720442411664.2024-07-08_15_15_43.mp4

logs (2).txt

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01ab200eebc7b06724
  • Upwork Job ID: 1810395750787214444
  • Last Price Increase: 2024-07-08
  • Automatic offers:
    • brunovjk | Reviewer | 103047644
    • nkdengineer | Contributor | 103047648
Issue OwnerCurrent Issue Owner: @allroundexperts

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