Repository navigation
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.4.18-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #93532
Email or phone of affected tester (no customers): ibellicotest+2766@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests
Action Performed:
Prerequisite: Account has at least one workspace.
- Open the Expensify app.
- Tap on FAB > "Create Expense" > "Scan"
- Create a scan expense with a receipt that will trigger a failure and submit it to workspace chat.
- Open the just created expense.
- Wait until receiving a Concierge message showing the scanning failure.
- Tap on "Explain" at the end of that message,
- Note that you land on a thread, and that skeleton loader is displayed for some time before messages are visible.
Expected Result:
After tapping on "Explain" on Concierge message after scan failure, user should land on a new created thread that should automatically load.
Actual Result:
Skeleton loader is displayed for some time when user navigates to thread after tapping on "Explain" link on Concierge message after scan expense failure.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7189308_1782277258832.Explain.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7189308
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022071452525536444275
- Upwork Job ID: 2071452525536444275
- Last Price Increase: 2026-07-13
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
applause-bot commentedon Jun 24, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/46abd74222963c01bf5de3a5516f77b064016ad32a030448b85d1a98bc4312da
melvin-bot commentedon Jun 24, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #93532
melvin-bot commentedon Jun 24, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 24, 2026
👋 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:
MelvinBot commentedon Jun 24, 2026
Issue Analysis
This is expected behavior, not a regression from #93532 — recommend removing the
DeployBlockerCashlabel and not reverting.The skeleton loader is generic to every
Explainthread, not specific to failed scans. Tapping any inlineExplainlink runs the sharedexplain()flow: if the explanation thread doesn't already exist, it creates an optimistic Concierge thread and firesOpenReport, and the thread screen showsReportActionsSkeletonViewuntil that request returns. PR #93532 added no scan-specific load logic — it only wiredRECEIPTSCANFAILEDmessages into the sameReportActionItemMessageWithExplain→explain()→createChildReport()→openReport()path already used byMovedTransactionAction,ExportIntegration,ModifiedExpenseContent,UnreportedTransactionAction, andApprovalFlowContent.Two facts back this up:
OpenReportround-trip latency / the explanation thread not yet existing, i.e. an environmental/timing difference, not a code change.hasReasoning()before this PR). [Payment due @brunovjk] Show Explain button on receipt scan failed system messages #93532 only made the affordance more discoverable.Recommendation: Remove
DeployBlockerCash. If the brief skeleton on freshly-created Explain threads is considered a real UX problem, it should be a separate, non-blocking issue scoped to the generic Explain/OpenReport loading experience — it affects all Explain actions equally and predates this PR.Investigation details (evidence)
Shared entry point — every
Explainlink runs the same handler:ReportActionItemMessageWithExplain.tsx:52-70—handleLinkPressdetectsCONCIERGE_EXPLAIN_LINK_PATHand callsexplain(childReport, originalReport, action, ...).Thread creation / fetch — the skeleton source:
Report/index.ts:2552-2592—const report = childReport ?? createChildReport(...). IfchildReportexists, it navigates straight to a populated thread (no skeleton). If not, a new optimistic thread is created.Report/index.ts:2485-2543—createChildReportcallsopenReport({ isNewThread: true, ... })for a brand-new thread.Report/index.ts:1500-1552—openReportoptimisticData setsisLoadingInitialReportActions: true; successData clears it. The skeleton-visible duration == theOpenReportround-trip latency.Skeleton gate — generic, no scan-failed branch:
ReportActionsView.tsx:178and:218-222—shouldShowSkeletonForInitialLoadkeyed onisLoadingInitialReportActions; rendersReportActionsSkeletonView. No receipt-scan logic here.Identical wiring across all Explain consumers —
childReportderived from the same Onyx key (REPORT + action.childReportID) and the sameoriginalReportfromActionContentRouter:ReceiptScanFailedContent.tsx:39, 48-55vs.MovedTransactionAction.tsx/UnreportedTransactionAction.tsx/ExportIntegration.tsx(byte-for-byte the samechildReportderivation). The scan-failed-only props (reportID,parentReportID, etc.) are used solely for thecanEditIOU-actor lookup, never for navigation.Alternative explanation considered: a genuine new slow path introduced by the PR. Ruled out — the PR's diff (
ReceiptScanFailedContent.tsx,ActionContentRouter.tsx,OriginalMessage.ts, tests) touches only rendering/typing, not theexplain()/openReportmachinery.Optional confirmation (not required): compare
OpenReportlatency (withisNewThread=true, originating from Explain taps) on staging vs production to confirm the staging-only repro is latency/thread-freshness, not a code difference.Next Steps for Contributor+ team:
To accept this assessment: remove the
DeployBlockerCashlabel (no revert needed). Optionally file a separate non-blocking issue for the generic Explain-thread loading UX.To refine:
@MelvinBot <your feedback>To reject: explain why you believe this is a true regression from #93532.
brunovjk commentedon Jun 24, 2026
I don’t think this is a regression from #93532. The PR only exposed the existing
Explainflow inline forRECEIPT_SCAN_FAILED.The skeleton is the normal shared loading state while a new Explain child thread is opened, so this looks like generic Explain-thread behavior rather than something introduced by the PR.
29 remaining items
brunovjk commentedon Jul 6, 2026
I think so, sorry.
melvin-bot commentedon Jul 9, 2026
@mollfpr, @abzokhattab Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jul 10, 2026
@mollfpr, @abzokhattab Huh... This is 4 days overdue. Who can take care of this?
mvtglobally commentedon Jul 11, 2026
Issue not reproducible during KI retests. (First week)
abzokhattab commentedon Jul 12, 2026
issue is not reproducible for me as well ... lets close this issue @mollfpr
Screen.Recording.2026-07-12.at.17.55.11.mov
melvin-bot commentedon Jul 13, 2026
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
melvin-bot commentedon Jul 15, 2026
@mollfpr, @abzokhattab Whoops! This issue is 2 days overdue. Let's get this updated quick!
mvtglobally commentedon Jul 17, 2026
Issue not reproducible during KI retests. (Second week)
brunovjk commentedon Jul 17, 2026
@mollfpr, can you help me close this issue? Thanks.