[$250] Attachment - Csv file uploaded with other files is not shown in chat

[jponikarchuk]

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: V9.3.11-15
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3846/folder/13176710/41236953/1156875326
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Chat Report View

Action Performed:

1. Launch app
2. Tap plus icon - attachment
3. Select a CSV file and an image
4. Send attachments
5. Note in preview only image is shown and csv file is missing

Expected Result:

Csv file uploaded with other files must be shown in chat

Actual Result:

Csv file uploaded with other files is not shown in chat but shown in preview.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7061718_1769762755027.Screenrecorder-2026-01-30-14-13-44-459.mp4

CSV_0.csv

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @truph01

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022029613321483038734
• Upwork Job ID: 2029613321483038734
• Last Price Increase: 2026-03-12

[mkzie2]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Csv file uploaded with other files is not shown in chat but shown in preview.

What is the root cause of that problem?

validateImageForCorruption immediately resolves if the file is not image:

App/src/libs/fileDownload/FileUtils.ts

Lines 285 to 287 in 0649d6e

	if (!Str.isImage(file.name ?? '') || !file.uri) {
	return Promise.resolve();
	}

Then for csv files - the file size is usually very small (<240 bytes), isFileCorrupted will return result as invalid here:

App/src/libs/AttachmentUtils.ts

Lines 78 to 83 in 0649d6e

	if (fileObject.size && fileObject.size < CONST.API_ATTACHMENT_VALIDATIONS.MIN_SIZE) {
	return {
	isValid: false,
	error: 'tooSmall',
	} satisfies AttachmentCorruptionValidationResult;
	}

Then "invalid" csv files will be filtered out here, and not displayed:

App/src/pages/media/AttachmentModalScreen/routes/report/ReportAddAttachmentModalContent/index.tsx

Lines 93 to 105 in 0649d6e

	if (Array.isArray(result)) {
	const validResults = result.filter((r) => r.isValid);
	if (validResults.length === 0) {
	return;
	}
	const validatedFiles = validResults.map((r) => r.file);
	const firstValidSource = validResults.at(0)?.source;
	setSource(firstValidSource);
	setValidFiles(validatedFiles);
	return;
	}

If we send only csv files, all files will be marked as "invalid", and the logic above returns early, so the validFiles is not changed. So the csv files are shown in that case.

App/src/pages/media/AttachmentModalScreen/routes/report/ReportAddAttachmentModalContent/index.tsx

Line 86 in 0649d6e

const [validFiles, setValidFiles] = useState<FileObject | FileObject[] | undefined>(fileParam);

What changes do you think we should make in order to solve the problem?

isFileCorrupted only checks for image integrity, so we should return early here if the file is not image:

    if (!Str.isImage(fileObject.name ?? '')) {
        return Promise.resolve({isValid: true});
    }

We can place that logic before here

App/src/libs/AttachmentUtils.ts

Line 69 in 0649d6e

return validateImageForCorruption(fileObject)

Or before here

App/src/libs/AttachmentUtils.ts

Line 71 in 0649d6e

if (fileObject.size && fileObject.size > CONST.API_ATTACHMENT_VALIDATIONS.MAX_SIZE) {

Or we only check the image logic in the minimum size calculation and leave the max size check as-is:

if (Str.isImage(fileObject.name ?? '') && fileObject.size && fileObject.size < CONST.API_ATTACHMENT_VALIDATIONS.MIN_SIZE) {

App/src/libs/AttachmentUtils.ts

Line 78 in 0649d6e

if (fileObject.size && fileObject.size < CONST.API_ATTACHMENT_VALIDATIONS.MIN_SIZE) {

What alternative solutions did you explore? (Optional)

N/A

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[cosmicvulpes]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When uploading a CSV file together with other files (like images), the CSV file is not displayed in the chat message, while the image appears correctly. The CSV file is visible in the preview, but once sent, only the image shows in the chat.

What is the root cause of that problem?

The root cause is in the isReportMessageAttachment function at src/libs/isReportMessageAttachment.ts.

When attachments are uploaded:

1. Each attachment gets its own report action with HTML representing the file
2. For images, the HTML is an <img> tag and the text is [Attachment]
3. For non-image files (CSV, PDF, etc.), the HTML is an <a> tag and the text is the filename (e.g., "CSV_0.csv")

The isReportMessageAttachment function checks:

• If text === "[Attachment]" → return true
• Else if Str.isVideo(text) → return true
• Otherwise → return false

For CSV files where text = "CSV_0.csv", both conditions fail, so the function returns false. This causes the fragment to render as TextCommentFragment (plain text filename) instead of AttachmentCommentFragment (clickable attachment with proper rendering).

What changes do you think we should make in order to solve the problem?

Modify isReportMessageAttachment to return true for any message that has the data-expensify-source attribute in its HTML, regardless of the text content. The presence of this attribute is the definitive marker that content is an Expensify attachment.

The fix simplifies the logic:

1. If HTML doesn't contain data-expensify-source → return false
2. If it does contain the attribute → return true

This ensures all attachment types (images, videos, CSV, PDF, etc.) are properly recognized and rendered as attachments.

What alternative solutions did you explore? (Optional)

N/A