WS - More feature - ON/Off button displayed instead feature

[mitarachim]

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.2.45-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: https://test-management.browserstack.com/projects/2219752/folder/13176744/test-cases/41237134
Email or phone of affected tester (no customers): applausetester+fish101123@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iOS
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com sign in with applause.expensifail.com
2. Go to Workspaces > More features

Expected Result:

All features should be visible.

Actual Result:

ON/Off button displayed instead feature

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

Bug6995371_1762376182059.ScreenRecording_11-05-2025_14-48-19_1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sonialiap (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 @thienlnam (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[melvin-bot]

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

[thienlnam]

Root Cause Identified

Caused by PR #73624 - "Make More Features animation more obvious and add tap target"

• PR Link: Make More Features animation more obvious and add tap target #73624
• Author: @nkdengineer
• Merged: 2025-11-05 at 02:33:55 UTC
• Included in: Staging release 9.2.45-0

The Issue

The PR restructured ToggleSettingOptionRow component in src/components/ToggleSettingOptionRow.tsx and wrapped the content area (containing feature titles and subtitles) in a PressableWithoutFeedback
component with accessible={false}.

<PressableWithoutFeedback
    style={[styles.flexRow, styles.alignItemsCenter, styles.flex1]}
    onPress={onPress}
    accessibilityLabel={title}
    role="button"
    accessible={false}  // <-- CAUSES RENDERING BUG ON iOS
>
    {contentArea}
</PressableWithoutFeedback>

Setting accessible={false} on a parent component causes child text elements to not render properly on iOS in React Native. This is a known iOS-specific rendering issue.