Skip to content

[Due for payment 2025-09-19] When merging per diem expense with manual expense, receipt cannot be viewed in full screen #68197

@nlemma

Description

@nlemma

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.1.91-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #65596
Email or phone of affected tester (no customers): jsdoijnsodisjo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Workspace has imported per diem rates.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit a per diem expense and a manual expense with receipt.
  4. Open expense report.
  5. Open the per diem expense.
  6. Click More > Merge.
  7. Select the manual expense with receipt > Continue.
  8. Select Receipt 2 from the manual expense > Continue.
  9. Select any detail for other field > Continue.
  10. On confirm page, open the receipt in full screen.

Expected Result:

The receipt will open in full screen.

Actual Result:

The receipt opens in full screen and closes immediately before it is loaded.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6911158_1754636087745.Screen_Recording_2025-08-08_at_14.48.49.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @kadiealexander

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions