Some of the required values for successive user emulation are missing. API output contains more details about what is missing.

Maybe there's some incorrect default in OB2 (e.g., string.Empty instead of null), and this is not a CaptchaSharp-specific bug.