BrowserAutomationStudio 25.3.0 has been released

[support]

Fixed issues with site isolation mode.

This mode allows you to place frames from different domains in different processes. Its absence can be detected by sites. Fixed: selector generation, getting cache, event emulation in touch screen mode. Last thing required a lot of modifications, and can affect not only the work in the frame itself, but also any page which contains isolated frames.

Added 3 new fingerprint factors related to system settings.

Improved display of software on monitors with high pixel density.

25.3.5

Added hls codec emulation for Android fingerprints.
Fixed issues with PC hang after several hours of work for compiled scripts.
Node has been updated up to 18.10.0 version.
Fixed some issues with touch mode in isolated frames.
Improved protection.

25.3.6

Lots of improvements for high pixel density monitors.

25.3.7

Chrome version updated to 107.0.5304.88
Improved touch emulation.

25.3.8

Improved PerfectCanvas code generation. Fixed issues on several sites.

[zzinan]

Is there a setting to adjust the software image to the old version? scaling is too big. :(

[GaG]

In "Settings" last opton is "Interface settings", there you have
"Zoom (%)" option, so adjust it to your needs.

[zzinan]

@GaG Thanks for answer. But there is only "restore original" option and this option does not work.

[Fox]

@zzinan said in BrowserAutomationStudio 25.3.0 has been released:

Is there a setting to adjust the software image to the old version? scaling is too big. :(

What is your screen resolution and what are the scaling settings in the operating system?

[GaG]

@zzinan

[zzinan]

@Fox 2560x1440 and 125% (recommended settings)

[zzinan]

[paul carfau]

Same for me. Running on Windows 10 64bits, and the scaling of the software have changed between the last version and the current version. I haven't changed anything on the settings.

[GaG]

And I like new scaling. I think its better than previous.

[hellomembersha]

checksum module no longer works with this update.
blake3 wasp is not suppported with this version of node is what my logs are stating

[thotho]

@paul-carfau same for me

[Fox]

A version with corrections has been released, a description of the changes in the topic header. The problem with the server hanging when using compiled scripts with protection has been fixed

[tibbar]

man, why does bas keep getting worse for you tube and google in every bas update. Instead of improving, it becomes more and more detectable

[Fox]

@tibbar said in BrowserAutomationStudio 25.3.0 has been released:

man, why does bas keep getting worse for you tube and google in every bas update. Instead of improving, it becomes more and more detectable

Even if we ignore the fact that google is constantly evolving, have you conducted comparisons and tests on different versions of BAS at the same time?

[tibbar]

@Fox Yes, previous versions work much better than 25.3.0 and 25.3.5 for y t and google. we had to revert to the previous versions to get it to work again. which is why I came to conclusion that bas dev probably dont check if the update they release ruins the antidetection for these sites. it just makes me not trust the updates they release anymore as I mainly only use bas for this purpose

[lowkeypal]

@tibbar which version are you using? and what in 25.3.0 version that make Google detectable?

[tibbar]

@Fox

@Fox said in Выпущена 25.3.0 версия BrowserAutomationStudio:

@uowner said in Выпущена 25.3.0 версия BrowserAutomationStudio:

Pixelscan:
Google/Youtube сильно фродят, через другие антидетект регистрируются аккаунты, через BAS гугл даже с подтверждением по смс не дает зарегать аккаунт. Версия 25.3.7

Используете ли вы отпечатки с perfectcanvas?

mine says error checking proxy usage, what does this mean?

[Fox]

@tibbar said in BrowserAutomationStudio 25.3.0 has been released:

mine says error checking proxy usage, what does this mean?

How exactly is your question related to the new version of BAS?

[tibbar]

@Fox this was in relation to the russian post about pixelscan detection but you move it here, now my reply no longer makes sense