Feature switch is enabled and cannot be disabled before the workspace is upgraded to Control

[IuliiaHerets]

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.0.70-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+kh1311020@applause.expensifail.com
Issue reported by: Applause Internal TEeam

Action Performed:

1. Go to staging.new.expensify.com
2. Create a Collect workspace.
3. Go to Workspace settings > More features.
4. Enable a Control plan feature (eg, Company cards).
5. Do not upgrade and dismiss the upgrade prompt.

Expected Result:

When toggling on a Control plan feature on a Collect workspace, the switch should remain disabled until the workspace is upgraded to Control plan (production behavior).

Actual Result:

When toggling on a Control plan feature on a Collect workspace, the switch is enabled even before workspace is upgraded to Control plan. When dismissing the upgrade prompt, the feature switch is still enabled. The toggle cannot be switched off too.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6682802_1733218552772.20241203_173143.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[IuliiaHerets]

Production

bandicam.2024-12-03.11-46-21-995.mp4

[shubham1206agra]

Same as #53447, and is fixed already.