Share to Expensify - File name is changed after Share to Expensify in offline mode

[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.2.3-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Prod, because of KI
If this was caught during regression testing, add the test name, ID and link from TestRail: #68997
Email or phone of affected tester (no customers): ndk.2303@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 11/iOS 18.6.2
App Component: Chat Report View

Action Performed:

1. Open native app
2. Login and keep it
3. Open internal device file folder
4. Go offline
5. Select a any file has name like this porin naduvil vikram whatsapp status #vikram #asuran #dhanrush #aniru #qu #instagram#subscribe_4.mp3
6. Share it to Expensify
7. After redirected to conversation, go online

Expected Result:

File is shared to Expensify conversation with the original name

Actual Result:

File is shared to Expensify conversation with a prefix string added to its name. String: 'File.... sharedFile'

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

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @flaviadefaria (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]

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

[melvin-bot]

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

[github-actions]

👋 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.

[NikkiWines]

@linhvovan29546 this looks like unintended/unaccounted for behavior from #68997, can you confirm if this is expected?