SessionNotCreatedException Message session not created This version of ChromeDriver only supports Chrome version 81

Encountering a SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81 error can be a significant roadblock for developers and QA engineers engaged in web automation. This specific exception often halts your Selenium WebDriver scripts dead in their tracks, preventing them from launching a Chrome browser instance. It’s a clear indicator of a version mismatch between the ChromeDriver executable you’re using and the installed Google Chrome browser on your system. Understanding the root cause of this common issue is crucial for efficient troubleshooting and maintaining robust automated testing environments. This guide will walk you through diagnosing and resolving this frustrating compatibility problem, ensuring your browser automation efforts remain smooth and effective.

Understanding the SessionNotCreatedException

The SessionNotCreatedException is a common error in Selenium WebDriver, signaling that the WebDriver was unable to start a new browser session. In this specific case, the message “This version of ChromeDriver only supports Chrome version 81” points directly to a crucial incompatibility. Selenium WebDriver requires a specific browser driver (like ChromeDriver for Google Chrome) to interact with the browser. This driver acts as a bridge, translating Selenium commands into actions the browser can understand and execute.

When you automate tasks using Selenium, your script initializes a WebDriver instance, which then attempts to launch the target browser using its corresponding driver. If the version of the Chrome browser installed on your machine does not align with the version of ChromeDriver you’re using, this communication breaks down. The error message explicitly states the supported Chrome version for the ChromeDriver you have. For instance, if you have ChromeDriver 81 but your Chrome browser has auto-updated to version 100, they simply won’t work together. This version mismatch is the primary culprit behind the SessionNotCreatedException.

According to the official Selenium WebDriver documentation, maintaining compatibility between your browser, its driver, and your Selenium library is paramount for stable test execution. Neglecting this crucial aspect can lead to unpredictable test failures and wasted debugging time. The browser driver must be updated regularly to match the evolving browser versions, especially with Chrome’s rapid release cycle.

The Core Problem: Version Mismatch

The core of the SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81 error lies in the strict versioning policy between Google Chrome and ChromeDriver. Each ChromeDriver release is designed to work with a specific range of Chrome browser versions. Google’s rapid release cycle for Chrome means that your browser can update automatically in the background, often leaving your static ChromeDriver executable outdated. This discrepancy is the most frequent cause of the SessionNotCreatedException.

For example, if your automated tests were developed when Chrome was at version 81, and you downloaded the corresponding ChromeDriver, everything would work fine. However, if Chrome then updates to version 82 (or any later version) while your ChromeDriver remains at the old version, you’ll encounter this error. The ChromeDriver effectively tells Selenium, “I can only speak the language of Chrome 81,” while your Chrome browser is speaking a newer dialect. This communication barrier prevents the session from being established, leading to the reported exception.

To prevent this, it’s essential to regularly check and align your ChromeDriver version with your installed Chrome browser. This proactive approach minimizes downtime and ensures the reliability of your automated testing suites or web scraping projects. Many developers overlook this basic maintenance, leading to hours of troubleshooting what is essentially a simple versioning problem.

Diagnosing the Chrome and ChromeDriver Version Mismatch

Before you can fix the SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81 error, you need to accurately identify the versions of both your Google Chrome browser and your ChromeDriver executable. This diagnosis is the most critical step in resolving the issue, as it provides the exact information needed to find the compatible driver.

It’s a common pitfall to assume you know the versions, but automatic updates or multiple installations can easily lead to incorrect assumptions. Taking a moment to verify ensures you’re applying the correct solution. For instance, you might have multiple versions of Chrome installed, or your system’s default browser might not be the one your tests are attempting to control.

Once you have both versions, you can cross-reference them with the official ChromeDriver downloads page. This page clearly lists which ChromeDriver version supports which Chrome browser versions. Generally, you want the ChromeDriver version to match the major version of your Chrome browser (e.g., Chrome 100 requires ChromeDriver 100). For more information on Chrome’s release channels and versions, you can consult the official Chrome Releases blog.

Verifying Your Chrome Browser Version

To check your Google Chrome browser version, follow these simple steps:

Open your Google Chrome browser.
Type chrome://version into the address bar and press Enter.
Look for the line that says “Google Chrome” followed by a version number (e.g., 100.0.4896.88). The first few numbers before the first dot represent the major version (e.g., 100).

This method provides the most accurate and up-to-date version of the Chrome browser installed on your system. It’s important to note that if you have multiple Chrome installations (e.g., stable, beta, dev, or canary channels), ensure you’re checking the version of the specific Chrome executable your Selenium script is attempting to launch. Often, the default path for ChromeDriver will point to your primary stable Chrome installation.

Identifying Your ChromeDriver Version

Identifying your current ChromeDriver version is equally straightforward. If you have the ChromeDriver executable in your system’s PATH, you can open a command prompt or terminal and type:

chromedriver --version

This command will output the version of the ChromeDriver executable. For example, it might return ChromeDriver 81.0.4044.138. If ChromeDriver is not in your PATH, navigate to the directory where you’ve stored the chromedriver.exe (or chromedriver on macOS/Linux) file and run the command from there. This step is critical because the error message specifically tells you which ChromeDriver version is causing the problem.

Knowing both your Chrome browser and ChromeDriver versions allows you to pinpoint the discrepancy. For instance, if your Chrome browser is version 100, but your ChromeDriver output shows version 81, then you’ve confirmed the exact cause of the SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81 error. This clear diagnosis sets you up for an effective resolution.

Effective Solutions to Resolve ChromeDriver Compatibility Issues

Once you’ve diagnosed the version mismatch causing the SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81, several effective solutions can Question & Answer :

I am currently new to robot framework.I am currently using latest window version of chrome and chromedriver which is 80 but when i try to run the test it gives the message “SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81” in pycharm but currently beta version of 81 is only available. I have tried uninstalling everthing and reinstalling it again but nothing works can anyone help me with this.Thank you!

Screenshots below:

I solved these kinds of problems using the webdrive manager.

You can automatically use the correct chromedriver by using the webdrive-manager. Install the webdrive-manager:

pip install webdriver-manager

Then use the driver in python as follows

from selenium import webdriver from webdriver_manager.chrome import ChromeDriverManager driver = webdriver.Chrome(ChromeDriverManager().install())

This answer is taken from https://stackoverflow.com/a/52878725