Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint

[makuma]

Hello,

I’m having a consistent issue specifically with Twitter/X when using FingerprintSwitcher in BAS.

✔ When FingerprintSwitcher is enabled:

Twitter instantly shows “Something went wrong”

Pages don’t load or actions fail

Login and normal browsing both trigger the same error

✔ When FingerprintSwitcher is disabled (no fingerprint applied):

Twitter works perfectly

No errors at all

Same proxy, same profile, same script — only difference is the fingerprint

Additional Notes:

I tested with many different fingerprints, same result

Proxy/IP does not matter — the issue happens only when fingerprint is applied

Without fingerprint, everything is stable

So this is not a proxy, browser, or script problem — seems fingerprint-specific

My question:

Is Twitter currently blocking BAS fingerprints?
Is this a known issue with FM3 / HumanEmulation?
Is there any recommended setting or workaround to avoid this detection?

Thanks in advance. 🙏

If you want, I can also add the exact error code, request ID, or screenshots.

[m4zuper]

I'll check it out, thanks for the information.

[makuma]

@m4zuper I look forward to hearing from you as soon as possible.

[makuma]

Hello,

I found a major difference between Record Mode and running the saved script, especially on X.com (Twitter). I tested this many times.

✔ Record Mode (works perfectly)

When I use Record Mode, I can create accounts without any problem.

I successfully created 100+ accounts

No errors

Email verification code is sent normally

No bot warning

Record Mode behaves like a real user.

✘ Running the saved script (Start button) — WITHOUT fingerprint

When I run the exact same script normally (Start button):

Twitter does not show “Something went wrong”

But it detects automation and shows something like:
“We detected unusual activity / You look like a bot”

Email verification code does not appear

I cannot create even one account

So even without fingerprint, Record Mode = works, Run Mode = detected.

✘ Running with FingerprintSwitcher (FM3) — WITH fingerprint

If I apply a fingerprint:

As soon as I click the Register button,

X.com instantly shows:
“Something went wrong”

No email code is sent

Signup fails immediately

Record Mode also fails when fingerprint is applied

This error only happens with fingerprint.

Summary
Mode Without Fingerprint With Fingerprint
Record Mode Works (100+ accounts) Fails instantly (“Something went wrong”)
Run Script Mode Bot detection on verification page Fails instantly (“Something went wrong”)
My Questions

Why does Record Mode behave differently than Run Mode?
(Same script, same actions, same steps.)

Why does X.com instantly show “Something went wrong” only when FM3 fingerprint is applied?

Is there anything internally different between Record Mode and normal execution?

Thank you.

[m4zuper]

I can't reproduce the issue.

Yes, I can't always register an account; the success rate is around 70%. But I still manage to register them. Apparently, registration success is influenced by a combination of parameters, such as the fingerprint and proxy.
Also, try using PerfectCanvas.

[makuma]

@m4zuper

My problem is that I constantly get an error like the one in the picture. When I use a fingerprint, I get this error, but if I don’t use it, there’s no issue — however, after I enter the email verification code, it sends me back to the previous step.