[BUG] Gemini settings: new installs can’t enable URL context/Search grounding (Save doesn’t activate)

[hannesrudolph]

Type

Bug

Problem / Value

On fresh setups or when settings are missing, toggling Gemini’s “Enable URL context” and “Enable Grounding with Google Search” does not register a change, so the Save button never activates. Users can’t enable these features.

Context

• App: 3.25.6
• Provider: Google Gemini
• Models: n/a (UI settings)
• Affects: New installs or users who removed these keys from exported settings and re-imported

Reproduction

1. Start with no prior Gemini settings (fresh install or import settings JSON without these keys)
2. Open Settings → Gemini
3. Toggle “Enable URL context” and/or “Enable Grounding with Google Search”
4. Observe: Save button does not become active, changes can’t be saved

Expected

Toggling either setting should register a state change and activate the Save button even if the setting key didn’t previously exist.

Actual

No tracked change occurs when the key doesn’t exist yet; Save remains inactive.

Acceptance Criteria

• Toggling these checkboxes creates/updates the setting keys and activates Save on first change
• Behavior consistent for both existing and missing keys
• No regression for other settings

Notes

See prior report for a related prompts Save-button activation issue; consider unifying change detection for settings that may not exist initially.

[roomote]

I'm exploring a potential fix for this issue where the Save button doesn't activate when toggling Gemini's URL context and Google Search grounding settings on fresh installs. I'll open a PR to share progress.

[roomote]

I've opened PR #8247 with a fix for this issue. The solution changes the checkbox checked prop from !!value to value === true to properly handle undefined states. This ensures the Save button activates when toggling these settings on fresh installs. The fix has been applied to both Gemini and Vertex components with comprehensive test coverage. Feedback welcome!