Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Config validation rejects bluebubbles enrichGroupParticipantsFromContacts [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#57295•Fetched 2026-04-08 01:51:26
View on GitHub
Comments
3
Participants
3
Timeline
4
Reactions
6
Author
jaserNo1jaserNo1
Participants
hassib-ashourihassib-ashourijaserNo1jaserNo1jmengitjmengit
Timeline (top)
commented ×3subscribed ×1

Error Message

GatewayRequestError: invalid config: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"

Root Cause

The bluebubbles runtime schema (config-schema-B0e8FgTR.js) defines the field with a default:

enrichGroupParticipantsFromContacts: z.boolean().optional().default(true)

When the UI reads the config, Zod parsing injects the default value. When saving back, the UI sends the full parsed config including this key. However, the validation schema (used by config.apply / openclaw config validate) does not recognize the key and rejects it in strict mode.

The key does not appear in openclaw.json on disk — it is injected by Zod default expansion during read.

Fix Action

Workaround

Edit config via CLI (openclaw config set ...) or direct JSON editing. The UI is blocked for all saves until this is fixed.

Code Example

GatewayRequestError: invalid config: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"

---

enrichGroupParticipantsFromContacts: z.boolean().optional().default(true)

---

openclaw config validate  # passes (key not in file)
# Add the key manually to openclaw.json under channels.bluebubbles
openclaw config validate  # fails with Unrecognized key
RAW_BUFFERClick to expand / collapse

Bug

After updating to OpenClaw 2026.3.24, saving any config change via the Control UI fails with:

GatewayRequestError: invalid config: channels.bluebubbles: Unrecognized key: "enrichGroupParticipantsFromContacts"

This blocks all UI config saves, not just bluebubbles changes.

Root Cause

The bluebubbles runtime schema (config-schema-B0e8FgTR.js) defines the field with a default:

enrichGroupParticipantsFromContacts: z.boolean().optional().default(true)

When the UI reads the config, Zod parsing injects the default value. When saving back, the UI sends the full parsed config including this key. However, the validation schema (used by config.apply / openclaw config validate) does not recognize the key and rejects it in strict mode.

The key does not appear in openclaw.json on disk — it is injected by Zod default expansion during read.

Steps to Reproduce

  1. Fresh install or update to 2026.3.24
  2. Have channels.bluebubbles configured (even minimally)
  3. Open Control UI, change any config setting, click Save
  4. Error: Unrecognized key: "enrichGroupParticipantsFromContacts"

Also reproducible via CLI:

openclaw config validate  # passes (key not in file)
# Add the key manually to openclaw.json under channels.bluebubbles
openclaw config validate  # fails with Unrecognized key

Expected Behavior

The validation schema should accept the same keys as the runtime schema, especially those with .default() values.

Workaround

Edit config via CLI (openclaw config set ...) or direct JSON editing. The UI is blocked for all saves until this is fixed.

Version

OpenClaw 2026.3.24

extent analysis

Fix Plan

To fix the issue, we need to update the validation schema to recognize the "enrichGroupParticipantsFromContacts" key.

  • Update the validation schema to include the missing key:
// In the validation schema file
channels: {
  bluebubbles: {
    // ... other fields ...
    enrichGroupParticipantsFromContacts: z.boolean().optional(),
  },
},
  • Alternatively, if the validation schema is generated automatically, ensure that it is regenerated to include the updated runtime schema.

Verification

To verify that the fix worked:

  1. Update the validation schema as described above.
  2. Try saving a config change via the Control UI.
  3. The save should succeed without the "Unrecognized key" error.

Extra Tips

  • Ensure that the runtime schema and validation schema are kept in sync to prevent similar issues in the future.
  • Consider automating the generation of the validation schema from the runtime schema to prevent manual errors.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#pipeline error#runtime error#dependency conflict#environment setup#docker error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING