[iOS][Feature Flags] Remove SAD flag for active and inactive users #2681
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task/Issue URL: https://app.asana.com/1/137249556945/project/1206329551987282/task/1211866611125558?focus=true
Tech Design URL:
CC:
Description
This PR removes two feature flags for SAD prompts:
Active Users
Commit: 60b2521
Feature Flag Task: https://app.asana.com/1/137249556945/project/1206329551987282/task/1211866611125558?focus=true
Inactive Users
Commit: 208a41a
Feature Flag Task: https://app.asana.com/1/137249556945/project/1206329551987282/task/1211866470962985?focus=true
Even though we use remote settings for the two prompts to function, the settings are defined in the parent feature, so it is safe to remove the subfeature from the codebase.
Testing Steps
DefaultBrowserPromptFeatureFlagger.swift->private func getSettings(_ value: DefaultBrowserPromptFeatureSettings) -> Intline 102.settingsProvider.defaultBrowserPromptFeatureSettings[value.rawValue] as? Intreturns a value and it’s not nil.Impact and Risks
<!—
What's the impact on users if something goes wrong?
High: Could affect user privacy, lose user data, break core functionality
Medium: Could disrupt specific features or user flows
Low: Minor visual changes, small bug fixes, improvement to existing features
None: Internal tooling, documentation
—>
What could go wrong?
Note
Removes active/inactive scheduled default browser prompt feature flags and gating, simplifying to use privacy-config settings only and updating factory, logic, and tests accordingly.
FeatureFlagcasesscheduledSetDefaultBrowserPromptsandscheduledSetDefaultBrowserPromptsForInactiveUsers, related override/support lists, and source mappings iniOS/Core/FeatureFlag.swift.SetAsDefaultAndAddToDockSubfeatureinPrivacyFeature.swift.DefaultBrowserPromptFeatureFlagAdapterto only exposedefaultBrowserPromptFeatureSettings(no enablement booleans).DefaultBrowserPromptFactoryno longer acceptsfeatureFlagProvider;DefaultBrowserPromptFeatureFlagnow constructed with onlysettingsProvider.DefaultBrowserPromptTypeDecideractive/inactive) and inDefaultBrowserPromptService.resume(); always record activity.DefaultBrowserPromptFeatureFlaggervalues.Written by Cursor Bugbot for commit f04cf27. This will update automatically on new commits. Configure here.