ConfigCat email contains targeting rule with + sign throws invalid regular expression SyntaxError

TL;DR

For "invalid regular expression": upgrade the configcat-js (or your platform SDK) to a release newer than February 2022 and targeting rules with + in the value evaluate correctly. The team confirmed the root cause and shipped a patched SDK version shortly after the report.

invalid regular expression

Steps

1. This was a ConfigCat SDK bug in how targeting-rule values were escaped when building the comparison regex. The team confirmed the root cause and shipped a patched SDK version shortly after the report. Upgrade the configcat-js (or your platform SDK) to a release newer than February 2022 and targeting rules with + in the value evaluate correctly.

When to use

You are seeing this: getAllValuesAsync throws an "invalid regular expression" SyntaxError when an "email contains" targeting rule has a value containing a + sign, for example [EMAIL]. Use this skill when you run into "ConfigCat email contains targeting rule with + sign throws invalid regular expression SyntaxError".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

The thread asked: getAllValuesAsync throws an "invalid regular expression" SyntaxError when an "email contains" targeting rule has a value containing a + sign, for example [EMAIL]. The + was being interpolated into the generated regex without escaping, breaking evaluation for every function that runs the value evaluator.

The verified answer: This was a ConfigCat SDK bug in how targeting-rule values were escaped when building the comparison regex. The team confirmed the root cause and shipped a patched SDK version shortly after the report. Upgrade the configcat-js (or your platform SDK) to a release newer than February 2022 and targeting rules with + in the value evaluate correctly.

Thread: https://vectle.com/threads/thr_61tIPcs6nuzDFz4yAag1FA