@mthuyet98 said in FingerprintManager not working:
It's too old 😄
What do you mean? The last FM3 update was 03/28/2025
f8e97d47-91d9-4c3b-985d-c2e44054b42f-изображение.png
I'm wondering what are the differences between v2 and v3 of Fingerprintmanager? Is there any change log available?
And can profiles created with FPM2 also be used in the latest version of BAS (24.0.8) or are these profiles not compatible with the new BAS?
Thank you for clarification.
@morpheus93 said in Difference between FPM2 und FPM3:
I'm wondering what are the differences between v2 and v3 of Fingerprintmanager? Is there any change log available?
And can profiles created with FPM2 also be used in the latest version of BAS (24.0.8) or are these profiles not compatible with the new BAS?
Thank you for clarification.
FM2 created on BAS version 23.2.2
FM3 created on BAS version 24.0.8
BAS 24 version differs from 23 by the new browser engine, FM2 profiles cannot be used in FM3 or BAS 24 version. Just like the FM3 profiles can't be used in the FM2 or BAS 23 version
@morpheus93 said in Difference between FPM2 und FPM3:
@Fox Thank you for clarification on this topic.
Any chance to get the issue with the missing click on the google cookie consent window (when using an IP from within the EU) fixed soon?
You can speed up this process by giving the helpdesk the fingerprints where the error occurs.
@Fox I think it's not related to specific fingerprints but affects all new profiles (with empty cache and cookies) that are generated and feeded with an IP address from within the EU when they visit google the 1st time. As the EU cookie law (ePrivacy Directive) engages every website owner to show those annoying "cookie consent" windows to visitors from the European Union.
In the "Human Emulation" mode of FPM3 the only thing that needs to be added is a check if the "cookie consent" window is visible when it goes to google and if yes, click on the "I agree/Ich stimme zu/..." (depending on the language of the shown google search page) button. After that click all should work as intended.

@morpheus93 said in Difference between FPM2 und FPM3:
@Fox I think it's not related to specific fingerprints but affects all new profiles (with empty cache and cookies) that are generated and feeded with an IP address from within the EU when they visit google the 1st time. As the EU cookie law (ePrivacy Directive) engages every website owner to show those annoying "cookie consent" windows to visitors from the European Union.
In the "Human Emulation" mode of FPM3 the only thing that needs to be added is a check if the "cookie consent" window is visible when it goes to google and if yes, click on the "I agree/Ich stimme zu/..." (depending on the language of the shown google search page) button. After that click all should work as intended.
In the "Human Emulation" script, there is a function that checks for the presence of this window and agrees to the conditions, if there is a window. However, a lot of time has passed since the development and Google selectors may have changed.
@Fox Yes, they probably changed the selector and now the function in the "Human Emulation" script can't find that cookie consent window/button any longer.
I assume I can not correct that myself, as the human emulation script is closed? So the only thing is to wait for a fix?
@morpheus93 said in Difference between FPM2 und FPM3:
@Fox Yes, they probably changed the selector and now the function in the "Human Emulation" script can't find that cookie consent window/button any longer.
I assume I can not correct that myself, as the human emulation script is closed? So the only thing is to wait for a fix?

Creating zip-files from the profile folders (C:\Users\Username\AppData\Local\BASProfileManager\PROFILEID) and sending it to the support email is okay? Or just the "fingerprint.json" file from within the profile folders?
@morpheus93 said in Difference between FPM2 und FPM3:
Creating zip-files from the profile folders (C:\Users\Username\AppData\Local\BASProfileManager\PROFILEID) and sending it to the support email is okay? Or just the "fingerprint.json" file from within the profile folders?
Both options are suitable
@Fox said in Difference between FPM2 und FPM3:
@morpheus93 said in Difference between FPM2 und FPM3:
Creating zip-files from the profile folders (C:\Users\Username\AppData\Local\BASProfileManager\PROFILEID) and sending it to the support email is okay? Or just the "fingerprint.json" file from within the profile folders?
Both options are suitable
Sent you some fingerprints via email. Hope this helps to solve the issue. Any estimated timeframe when the script is working again with google (from European IPs)?
Thank you.
@morpheus93 said in Difference between FPM2 und FPM3:
Sent you some fingerprints via email. Hope this helps to solve the issue. Any estimated timeframe when the script is working again with google (from European IPs)?
Thank you.
Fixed it