You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-07-17] Expense - Skeleton loader appears briefly after creating expense in the empty report #95698
Version Number: 9.4.32-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:#95045 Email or phone of affected tester (no customers):sidbhisdhidhisdhis@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an empty report.
Open the report.
Create an expense inside the report.
Expected Result:
Skeleton loader will not appear after creating expense in the empty report.
Actual Result:
Skeleton loader appears briefly after creating expense in the empty report.
👋 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:
Identify the pull request that introduced this issue and revert it.
TL;DR:PR #95045 (the PR this deploy blocker was auto-assigned to) is very unlikely to be the cause. Its changes are purely FlashList scroll-positioning and it does not touch any of the code that controls the skeleton loader's visibility. The transient skeleton is gated by a data-readiness state that flips while the first expense is created.
Why it's not #95045: The skeleton (ReportActionsSkeletonView) and the FlashList are mutually-exclusive siblings — ReportActionsSkeletonGuard renders the skeleton instead of the list. Which one shows is decided entirely by computeReportActionsSkeletonState, whose inputs are all data-readiness signals (isLoadingInitialReportActions, isMissingReportActions, isSingleExpenseReport, isOffline, …). None of them read initialScrollIndex or FlashList paint timing.#95045 only edits scroll files (useReportActionsScroll.ts, ReportActionsList.tsx, the flash-list patch, etc.) — none of the three skeleton-gating files. Even the new "delayed first paint" patch behavior happens inside the already-mounted list, so it can only yield a blank list frame, never re-show the skeleton.
Most likely cause: A data-readiness flip in computeReportActionsSkeletonState at the moment the expense is created:
Recommended next step: Since this is time-sensitive, I'd suggest not reverting #95045 based on this. Instead, look at which PR in this StagingDeployCash actually touched the report-actions loading / skeleton logic (ReportActionsListContext.tsx, useReportActionsListModel.ts, ReportActionsSkeletonGuard.tsx), and confirm on staging with a debugger whether the skeleton coincides with isSingleExpenseReport && !transactionThreadReport?.reportID. Production logs / a screen recording with those state values would confirm the exact trigger.
Investigation details
Confidence: High that #95045 is not the cause (based on its diff + the structural independence of skeleton vs. scroll code). Medium on the exact root cause, since I did not capture runtime state.
Open linked message at top - 3 #95045's initialScrollIndex delaying first paint → the delay is internal to the mounted FlashList, which sits in the guard's children; it cannot bring the skeleton back. Would show a blank list, not a skeleton.
Report type flipping shouldFocusToTopOnMount on expense creation → shouldReportAlignToTop is type-based (money-request report), not a function of whether expenses exist, so it doesn't flip when the expense is added.
List remount when initialScrollIndex changes → the list is keyed by key={listID}, not initialScrollIndex, so no remount occurs.
Next Steps: Reply with @MelvinBot <your feedback> to refine this analysis (e.g. point me at the other PRs in this deploy and I can narrow down which one changed the skeleton logic).
changed the title [-]Expense - Skeleton loader appears briefly after creating expense in the empty report[/-][+][Due for payment 2026-07-17] Expense - Skeleton loader appears briefly after creating expense in the empty report[/+]on Jul 10, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.32-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@mountiny The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
@mountiny The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Jul 9, 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/0bd5efe862c6509ec350d7bd500bfc20742571236416f7233c0ce30bf22c7703
melvin-bot commentedon Jul 9, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #95045
melvin-bot commentedon Jul 9, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jul 9, 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 Jul 9, 2026
Issue Analysis
TL;DR: PR #95045 (the PR this deploy blocker was auto-assigned to) is very unlikely to be the cause. Its changes are purely FlashList scroll-positioning and it does not touch any of the code that controls the skeleton loader's visibility. The transient skeleton is gated by a data-readiness state that flips while the first expense is created.
Why it's not #95045: The skeleton (
ReportActionsSkeletonView) and the FlashList are mutually-exclusive siblings —ReportActionsSkeletonGuardrenders the skeleton instead of the list. Which one shows is decided entirely bycomputeReportActionsSkeletonState, whose inputs are all data-readiness signals (isLoadingInitialReportActions,isMissingReportActions,isSingleExpenseReport,isOffline, …). None of them readinitialScrollIndexor FlashList paint timing. #95045 only edits scroll files (useReportActionsScroll.ts,ReportActionsList.tsx, the flash-list patch, etc.) — none of the three skeleton-gating files. Even the new "delayed first paint" patch behavior happens inside the already-mounted list, so it can only yield a blank list frame, never re-show the skeleton.Most likely cause: A data-readiness flip in
computeReportActionsSkeletonStateat the moment the expense is created:isReportDataIncomplete = isSingleExpenseReport && isMissingTransactionThreadReportID— creating the first expense makeschildMoneyRequestCount === 1(soisSingleExpenseReport→ true) for a frame before the transaction-thread report ID populates, which (with a transientisLoadingInitialReportActions) tripsshouldShowSkeletonForInitialLoad. This is the strongest candidate.hasDerivedValueTimingIssue = reportActionsLength > 0 && isMissingReportActions— a window where raw actions exist but the derivedsortedVisibleReportActionsis momentarily empty during recompute.Recommended next step: Since this is time-sensitive, I'd suggest not reverting #95045 based on this. Instead, look at which PR in this StagingDeployCash actually touched the report-actions loading / skeleton logic (
ReportActionsListContext.tsx,useReportActionsListModel.ts,ReportActionsSkeletonGuard.tsx), and confirm on staging with a debugger whether the skeleton coincides withisSingleExpenseReport && !transactionThreadReport?.reportID. Production logs / a screen recording with those state values would confirm the exact trigger.Investigation details
Confidence: High that #95045 is not the cause (based on its diff + the structural independence of skeleton vs. scroll code). Medium on the exact root cause, since I did not capture runtime state.
Key references:
ReportActionsSkeletonGuard.tsx:31-64ReportActionsListContext.tsx:44-119(:84,:86,:109,:112)isMissingReportActions/isSingleExpenseReport:useReportActionsListModel.tsuseReportActionsScroll.ts:415-423Alternatives considered & ruled out:
initialScrollIndexdelaying first paint → the delay is internal to the mounted FlashList, which sits in the guard'schildren; it cannot bring the skeleton back. Would show a blank list, not a skeleton.shouldFocusToTopOnMounton expense creation →shouldReportAlignToTopis type-based (money-request report), not a function of whether expenses exist, so it doesn't flip when the expense is added.initialScrollIndexchanges → the list is keyed bykey={listID}, notinitialScrollIndex, so no remount occurs.Next Steps: Reply with
@MelvinBot <your feedback>to refine this analysis (e.g. point me at the other PRs in this deploy and I can narrow down which one changed the skeleton logic).aimane-chnaif commentedon Jul 9, 2026
I am not sure this was caused by #95045. This was not reproducible at the time of PR review.
VickyStash commentedon Jul 9, 2026
QA mentions this as causing PR: #95287
m-natarajan commentedon Jul 9, 2026
Repro, Chrome / v9.4.32-1
REC-20260709204847.mp4
Not repro on iPhone 11/26.2 Build v9.4.32-1
RPReplay_Final1783620815.MP4
7 remaining items
[-]Expense - Skeleton loader appears briefly after creating expense in the empty report[/-][+][Due for payment 2026-07-17] Expense - Skeleton loader appears briefly after creating expense in the empty report[/+]melvin-bot commentedon Jul 10, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 10, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.32-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-07-17. 🎊
melvin-bot commentedon Jul 10, 2026
@mountiny The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Jul 14, 2026
@mountiny The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
lanitochka17 commentedon Jul 28, 2026
Deploy Blocker #97250 was identified to be related to the PR #96785 that attempted to fix this issue.