In Multilogin, we normally provide new browser core versions with one- or two-week delay from their official release. The cores are then updated automatically on profile launch. In this article, we will explain why such delays are actually useful.

Why it is better to wait

In the world of online privacy, staying ahead of the curve is paramount. So, when Chrome or Firefox roll out their new browser core, your first thought is to, probably, update your antidetect right away.

However, it is a common misconception. Updating the browser core to the latest version immediately upon its release is not the best practice. Here's why.

• Vulnerability issues: The official Chrome/Firefox core release often serves as a testing ground for new features and security patches. While they are intended to enhance user experience and security, it is best to adopt them after thorough testing and refinement are done by the publisher 🕵️
• Possible bugs: Delaying the update allows developers to observe and address any potential issues that may arise following the official release. This proactive approach minimizes disruption for users and ensures a smoother transition to the updated core 🐞
• Bans and restrictions: Some websites do not incorporate the new cores right away. Updating the core too quickly may lead to unexpected results and account restrictions. By waiting for the wider adoption of the new core, you can ensure compatibility and reduce the risks of being detected 🛑
• Automation compatibility: Tools like Puppeteer, Selenium, and other web-scraping or testing frameworks rely heavily on browser functionalities. They frequently experience compatibility issues with the latest cores and need time to adjust their APIs and features accordingly 🤖

Controlling core updates via API

You can use the auto_update_core parameter to specify if your browser profiles will update automatically as soon as new cores are released. It can be used in the Start Quick Profile, Profile Create, and Profile Update endpoints. 

• Enable automatic updates (default): If auto_update_core is true, the profile will automatically update to the latest core version

"auto_update_core": true,

• Disable automatic updates: Set auto_update_core to false and specify the required core_version

"core_version": 130,
"auto_update_core": false,

Consider the following while using this feature:

• If the parameter auto_update_core is left unspecified when using the Profile Update endpoint, it will reset back to true, its default state
• If you want to keep your current core version, you must ensure that the auto_update_core flag is set to false, preventing it from being automatically updated
• When updating a profile, changing the core version to anything other than the latest version is not supported
• We recommend using the default settings, which ensure your browser cores stay up-to-date – Multilogin is not responsible for any bans or detection issues if profiles are using an outdated core version

Troubleshooting

Normally, a browser core should be downloaded within 10 minutes. Here's what you can do if this process is taking longer than expected:

• Uninstall 3rd party apps: Antivirus, firewall, VPN, and proxy apps (such as Proxifier and SocksEscort) may interrupt Multilogin connections
• Change your internet connection: Your ISP may block certain websites, including Multilogin – to rule out this possibility, try connecting to a different Wi-Fi network or use a mobile hotspot
• Reconnect the agent: This can help if related processes have been interrupted and are not running correctly
• Reinstall the app components: This way the app will download all the necessary components for smooth operations (you won't lose any data)
• Check your system language: In some cases, the download process can be stuck if your OS language is not English