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
Status - Status button and set status is not displayed in the settings RHP #95702
👋 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.
Classification: Frontend bug (App) — but no App PR modifies the affected rendering path (see analysis) Causing PR: None confirmed. Only App PR touching ProfilePage.tsx this release is #95421 - "Restore Wallet and other Account sections for agent accounts" by @NicolasBonet (Low confidence — does not touch the Status row) Related Issues: N/A
Recommendation: NEEDS INVESTIGATION
The code that renders the Status row on the Profile settings page is byte-for-byte identical to production (9.4.31-0) — no App PR in this release changed the Status rendering, its gating, the CustomStatus pages, or the shared MenuItem/Section components. I could not tie the symptom to a code change, so I am keeping the DeployBlockerCash label and requesting more info rather than removing it.
Assigned: @NicolasBonet (PR author), @cretadn22, @yuwenmemon (approving reviewers) of #95421 — the only Profile-page change this release, for context (low confidence it is the cause). Labels: No change. DeployBlockerCash kept (issue not shown to be non-App, and label was auto-assigned by melvin-bot, not manually removed-eligible).
📋 Detailed Analysis
Evidence
The Status menu item is rendered from the publicOptions array in ProfilePage.tsx and mapped into MenuItemWithTopDescription rows. The Status entry renders unconditionally (it is not behind isAgentAccount, a beta, or any canUseXYZ gate).
I diffed ProfilePage.tsx between production tag 9.4.31-0 and staging HEAD a2304e2bb7b8a6e169ebef55d10c6b9b157b3b5f (PR Restore Wallet and other Account sections for agent accounts #95421). The only changes are to the Contact Methods entry (removing isAgentAccount gating) and to the private section wrapper. The Status option block is unchanged.
Bug is reported staging-only, web-only (Windows/Chrome, macOS/Chrome/Safari), not on mobile — a signal that usually implies a platform-specific or shared-component regression, but none is present here (there is no ProfilePage.web.tsx; a single ProfilePage.tsx serves all platforms).
Status detail page (used when the row is tapped): src/pages/settings/Profile/CustomStatus/StatusPage.tsx — route SETTINGS.PROFILE.STATUS still registered at ModalStackNavigators/index.tsx#L500. Neither StatusPage.tsx nor the navigator's Status route changed this release.
Files changed between 9.4.31-0 and HEAD in the relevant area: only ProfilePage.tsx (and Avatar-related files). Not changed this release:MenuItem.tsx, MenuItemWithTopDescription.tsx, Section/index.tsx, any CustomStatus/* page, useCurrentUserPersonalDetails, or the status field in personal-details utils.
Root Cause
Unconfirmed from App code. Since the entire Status rendering path is unchanged from production, the most likely explanations are:
Data/backend: currentUserPersonalDetails.status (emojiCode/text) not being returned/populated on staging, which matches "setting a status also does not display it." The row's title is emojiCode ? \${emojiCode} ${text}` : ''` — an empty status yields an empty title while the "Status" description still renders. If the description is genuinely missing too, that points to data upstream rather than this component.
Repro/environment specific: possibly a specific (e.g. agent) account or a staging-only data state.
What we need to proceed
The screen recording / screenshot for this account, confirming whether the "Status" label row is missing entirely, or only the set-status value is missing.
Whether the affected account is an agent account.
A request_id from the OpenApp/UpdateStatus call on staging so we can confirm whether the backend returns the status field on personalDetails.
If it turns out the backend is not returning the status field for a correctly-formed request, this is a Backend bug and DeployBlockerCash should be removed in favor of DeployBlocker. Until confirmed, we keep DeployBlockerCash.
Unless I'm misunderstanding something, I do not think this is not a bug but is intentional based on the change that went live on the linked PR. This was the proposed solution in #92253 which is linked to PR #93393.
Proposed Solution
Improve the Accounts page to make Copilot switching more immediately accessible by:
Replacing the Status icon with a Switch button for switching to different copilot accounts
Move Status to the Profile page
Add a tooltip for whenever someone goes to Accounts for the first time after being added as a copilot (or if we have a tooltip already, we'd update it).
Since we're adding the switch button, then we no longer need to make the email + profile photo clickable.
Move the Copilot Access tooltip to the Switch button instead of leaving it in its current location
The problem here seems to be that the new Switch button is not displaying where the status icon used to be.
I dug into whether #95421 could be the cause, but that PR only restores Account sections (Wallet, Preferences, Subscription, contact methods, private details) that were previously hidden for agent accounts — it doesn't touch the Status row on the Profile page or the status button in the Account settings page, and the entire Status rendering path is byte-for-byte unchanged from production. The missing status button instead comes from #93393 in this same release, which intentionally replaced the Status icon on the Account page with the Copilot Switch button and moved Status to the Profile page (per #92253), so this is expected behavior rather than a regression from #95421.
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/aa8019cd7f07e625d09cf90ed0bba1ed70321a759c438a75a1a94a7e66d058b6
melvin-bot commentedon Jul 9, 2026
Triggered auto assignment to @flodnv (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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
🔍 Investigation Summary
Classification: Frontend bug (App) — but no App PR modifies the affected rendering path (see analysis)
Causing PR: None confirmed. Only App PR touching
ProfilePage.tsxthis release is #95421 - "Restore Wallet and other Account sections for agent accounts" by @NicolasBonet (Low confidence — does not touch the Status row)Related Issues: N/A
Recommendation: NEEDS INVESTIGATION
The code that renders the Status row on the Profile settings page is byte-for-byte identical to production (9.4.31-0) — no App PR in this release changed the Status rendering, its gating, the CustomStatus pages, or the shared
MenuItem/Sectioncomponents. I could not tie the symptom to a code change, so I am keeping theDeployBlockerCashlabel and requesting more info rather than removing it.Assigned: @NicolasBonet (PR author), @cretadn22, @yuwenmemon (approving reviewers) of #95421 — the only Profile-page change this release, for context (low confidence it is the cause).
Labels: No change.
DeployBlockerCashkept (issue not shown to be non-App, and label was auto-assigned by melvin-bot, not manually removed-eligible).📋 Detailed Analysis
Evidence
publicOptionsarray inProfilePage.tsxand mapped intoMenuItemWithTopDescriptionrows. The Status entry renders unconditionally (it is not behindisAgentAccount, a beta, or anycanUseXYZgate).ProfilePage.tsxbetween production tag9.4.31-0and staging HEADa2304e2bb7b8a6e169ebef55d10c6b9b157b3b5f(PR Restore Wallet and other Account sections for agent accounts #95421). The only changes are to the Contact Methods entry (removingisAgentAccountgating) and to the private section wrapper. The Status option block is unchanged.ProfilePage.web.tsx; a singleProfilePage.tsxserves all platforms).Verification
src/pages/settings/Profile/ProfilePage.tsxsrc/pages/settings/Profile/CustomStatus/StatusPage.tsx— routeSETTINGS.PROFILE.STATUSstill registered at ModalStackNavigators/index.tsx#L500. NeitherStatusPage.tsxnor the navigator's Status route changed this release.9.4.31-0and HEAD in the relevant area: onlyProfilePage.tsx(and Avatar-related files). Not changed this release:MenuItem.tsx,MenuItemWithTopDescription.tsx,Section/index.tsx, anyCustomStatus/*page,useCurrentUserPersonalDetails, or the status field in personal-details utils.Root Cause
Unconfirmed from App code. Since the entire Status rendering path is unchanged from production, the most likely explanations are:
currentUserPersonalDetails.status(emojiCode/text) not being returned/populated on staging, which matches "setting a status also does not display it." The row'stitleisemojiCode ? \${emojiCode} ${text}` : ''` — an empty status yields an empty title while the "Status" description still renders. If the description is genuinely missing too, that points to data upstream rather than this component.What we need to proceed
request_idfrom theOpenApp/UpdateStatuscall on staging so we can confirm whether the backend returns thestatusfield onpersonalDetails.If it turns out the backend is not returning the
statusfield for a correctly-formed request, this is a Backend bug andDeployBlockerCashshould be removed in favor ofDeployBlocker. Until confirmed, we keepDeployBlockerCash.flaviadefaria commentedon Jul 9, 2026
Unless I'm misunderstanding something, I do not think this is not a bug but is intentional based on the change that went live on the linked PR. This was the proposed solution in #92253 which is linked to PR #93393.
The problem here seems to be that the new
Switchbutton is not displaying where the status icon used to be.flaviadefaria commentedon Jul 9, 2026
cc @wildan-m @eh2077 @inimaga
wildan-m commentedon Jul 9, 2026
@flaviadefaria is that test account have copilot access to another account?
NicolasBonet commentedon Jul 9, 2026
I dug into whether #95421 could be the cause, but that PR only restores Account sections (Wallet, Preferences, Subscription, contact methods, private details) that were previously hidden for agent accounts — it doesn't touch the Status row on the Profile page or the status button in the Account settings page, and the entire Status rendering path is byte-for-byte unchanged from production. The missing status button instead comes from #93393 in this same release, which intentionally replaced the Status icon on the Account page with the Copilot Switch button and moved Status to the Profile page (per #92253), so this is expected behavior rather than a regression from #95421.
inimaga commentedon Jul 9, 2026
@flaviadefaria Yes. This is expected behaviour and shouldn't have been flagged as a deploy blocker. We can safely close.