Require Attendees - Require attendees option missing in category settings

[lanitochka17]

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.10-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79741
Email or phone of affected tester (no customers): kiatest.78+ck12726100@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: iPhone 16/iOS 18.7.1
App Component: Workspace Settings

Action Performed:

1. Launch Hybrid app
2. Create new account & workspace
3. Enable Rules in More features
4. Go to Rules
5. Enable Attendee tracking
6. Go to categories
7. Select any category
8. SElect Required Fields

Expected Result:

Require Attendees option to be available in Category settings to enable it

Actual Result:

Require attendees option missing in category settings

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7059647_1769549236914.ScreenRecording_01-27-2026_16-17-11_1.1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @linhvovan29546

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @linhvovan29546 (External)

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[ikevin127]

Discussing in the PR: that follow-up PR added a specific dev / staging lock on the feature which could mean that the feature is disabled on builds that fall outside of that lock / edge case for the Config?.ENVIRONMENT checks on native.

[JS00001]

@ikevin127 If there are regressions, lets just do this in a follow up since its disabled

[ikevin127]

The thing is, in the latest follow-up I conditionally enabled / disabled the feature flag like so:

IS_ATTENDEES_REQUIRED_ENABLED: !Config?.ENVIRONMENT || Config?.ENVIRONMENT === 'staging' || Config?.ENVIRONMENT === 'development',

problem seems to be that on the native (iOS / Android) the feature is not showing according to QA, but it does on web-based platforms so I'm wondering whether we should remove the feature flag or change the conditions ?

I'm thinking that since on web the feature works, the Config?.ENVIRONMENT dev / staging checks don't work as on web / returning false on native and I'm not sure how to go about checking this.