[$250] Workspace - Workspace created on landscape mode is not visible on list until scroling.

[applause-bot]

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.3.97-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: http://github.com/Expensify/App/pull/91305
Email or phone of affected tester (no customers): ibellicotest+2757@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Workspace Settings

Action Performed:

Prerequisite: Account has no workspaces yet.

1. Open the Expensify app.
2. Navigate to "Workspaces"
3. Turn to landscape mode.
4. Scroll down and tap on "New Workspace" > "Confirm"
5. Once you land on new workspace menu, tap on the back arrow on the top left corner.
6. Note that new created workspace is not visible on workspaces list.
7. Scroll down.
8. Note that workspace preview appears while scrolling,

Expected Result:

First created workspace should be automatically visible on workspaces list.

Actual Result:

First created workspace is not visible on workspaces list until scrolling if it was created while on landscape mode.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7170106_1780455590061.WS_Landscape.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7170106

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022062609056140341344
• Upwork Job ID: 2062609056140341344
• Last Price Increase: 2026-06-04

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/5259d767153d72a9e8c5f71cd52271d5f90e016b0ea86d234b3898653497d38b

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91305

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

[MelvinBot]

Proposal

Heads up — this deploy blocker looks misassigned. It was auto-assigned to the author of #91305 (workspace scoped roles), but that PR only touches individual workspace pages and does not touch the Workspaces list, the empty state, or the Table component. The regression comes from #90204 ("Update workspaces page to use the table component"), which migrated this screen to FlashList and merged into the same 9.3.97 staging build. The BrowserStack link field in the report points at #91305, but the file evidence points at #90204.

What is the root cause of that problem?

The Workspaces list was migrated from SelectionList to a FlashList-based Table component in #90204. The new list renders the empty state and the rows through the same FlashList instance — the empty state is passed as ListEmptyComponent, and the content container toggles flexGrow1 on/off depending on whether there are rows.

When you rotate to landscape while the list is empty (no workspaces yet), then create the first workspace and return, FlashList does not re-measure its layout for the empty→populated transition that happened across an orientation change. The new row is inserted using stale layout/offset data, so it renders below the visible viewport. Any scroll forces a re-layout, which is why "the workspace preview appears while scrolling." In portrait this doesn't reproduce, which is consistent with a measurement/orientation issue rather than a data issue (the policy is correctly in Onyx — only its rendered position is wrong).

Evidence

• Real culprit: Expensify/App#90204 (merged 2026-06-01 20:43 UTC) migrated the list to Table/FlashList. The blamed Expensify/App#91305 (merged 2026-06-01 16:08 UTC) does not touch WorkspacesListPage, WorkspacesEmptyStateComponent, or src/components/Table/*.
• FlashList instance + dynamic empty-state styling: TableBody.tsx:91-98 — note ListEmptyComponent and contentContainerStyle={[filteredAndSortedData.length === 0 && styles.flexGrow1, ...]} which changes when data goes 0→1.
• Empty state wired through the same list: WorkspaceListTable/index.tsx:107.
• List render site: WorkspacesListPage.tsx:644-647.
• @shopify/flash-list is at 2.3.0 (FlashList v2, auto-measuring). The Table component has no orientation/useWindowDimensions handling to force a recompute on rotation.

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

Force FlashList to re-measure when the layout that produced the empty state is no longer valid. Two viable directions (team should pick after verifying on a landscape Android device):

1. Stop mutating the FlashList contentContainerStyle on the 0→1 transition. Move the empty-state flexGrow1 fill into the ListEmptyComponent wrapper itself instead of toggling it on the shared contentContainerStyle in TableBody.tsx:98. This removes the layout-changing style flip that coincides with the first row appearing.
2. Re-key/recompute the list on orientation change — derive a key (or call a recompute) from useWindowDimensions() width in TableBody so FlashList re-lays out after rotation.

Because this is a time-sensitive deploy blocker, the standard alternative is to revert #90204 if a forward fix can't be verified quickly.

What alternative solutions did you explore? (Optional)

• Revert Update workspaces page to use the table component #90204 (cleanest per deploy-blocker protocol if no quick forward fix).
• Re-assign this blocker to the author/reviewers of Update workspaces page to use the table component #90204 rather than Implement read-only access to workspace pages #91305.

---

⚠️ Confidence: Medium. The culprit-PR identification is high confidence (file diffs + merge timing). The exact FlashList internal mechanism and the precise fix are inferred — I could not reproduce the Android-native landscape flow here, so the fix should be validated on a real device in landscape.

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/92475) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[mitarachim]

production build from playstore still 9.3.90-3 and we cannot reproduce this issue in this build due to different behavior

2026-06-03.11.47.58.AM.mp4

However, issue is reproducible when using the same APK version as the production web build (v9.3.94-0)

2026-06-03.11.49.40.AM.mp4