-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Description
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.2.29-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1237/41237997/945417200?q=drag&issue_type=jira
Email or phone of affected tester (no customers): jsdoinjsoijsiodj@gmail.com
Issue reported by: Applause - Internal Team
Action Performed:
- Go to staging.new.expensify.com
- Go to workspace chat
- Click + > Create expense > Scan
- Drag and drop a video to the Scan RHP
→ Invalid file type error shows up - Expected behavior - Close the RHP
- Drag and drop a video to Scan zone
- Click Create expense
- Open the expense thread
Expected Result:
"Invalid file type" error will show up when dropping a video to Scan zone in workspace chat
Actual Result:
User can create a scan expense with video as receipt by dropping a video to Scan zone in workspace chat
There is no "Invalid file type" error
After creating the expense, error shows up in transaction thread
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Bug6972307_1760211709021.video_receipt.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021977603641386532131
- Upwork Job ID: 1977603641386532131
- Last Price Increase: 2025-10-27
Issue Owner
Current Issue Owner: @kadiealexanderMetadata
Metadata
Labels
Type
Projects
Status