You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.en.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,6 +146,23 @@ like when the last tab/browser has closed (e.g. `driver.close()`)
146
146
Check your script for instances of `driver.close()` and `driver.quit()`, and any other possible causes
147
147
of closed tabs/browsers. It could be that you are locating an element before you should/can.
148
148
149
+
## SessionNotCreatedException
150
+
151
+
This exception occurs when the WebDriver is unable to create a new session for the browser. This often happens due to version mismatches, system-level restrictions, or configuration issues.
152
+
153
+
### Likely Cause
154
+
155
+
- The browser version and WebDriver version are incompatible (e.g., ChromeDriver v113 with Chrome v115).
156
+
- macOS privacy settings may block the WebDriver from running.
157
+
- The WebDriver binary is missing, inaccessible, or lacks the necessary execution permissions (e.g., on Linux/macOS, the driver file may not be executable).
158
+
159
+
160
+
### Possible Solutions
161
+
162
+
- Ensure the WebDriver version matches the browser version. For Chrome, check the browser version at `chrome://settings/help` and download the matching driver from [ChromeDriver Downloads](https://chromedriver.chromium.org/downloads).
163
+
- On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
164
+
- Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
165
+
149
166
## ElementNotVisibleException
150
167
151
168
This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible.
@@ -160,4 +177,4 @@ This can occur in several situations:
160
177
161
178
This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following:
162
179
using an explicit wait, or interacting with the page in such a way to make the element visible
Copy file name to clipboardExpand all lines: website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.ja.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,6 +142,23 @@ like when the last tab/browser has closed (e.g. `driver.close()`)
142
142
Check your script for instances of `driver.close()` and `driver.quit()`, and any other possible causes of closed
143
143
tabs/browsers. It could be that you are locating an element before you should/can.
144
144
145
+
## SessionNotCreatedException
146
+
147
+
This exception occurs when the WebDriver is unable to create a new session for the browser. This often happens due to version mismatches, system-level restrictions, or configuration issues.
148
+
149
+
### Likely Cause
150
+
151
+
- The browser version and WebDriver version are incompatible (e.g., ChromeDriver v113 with Chrome v115).
152
+
- macOS privacy settings may block the WebDriver from running.
153
+
- The WebDriver binary is missing, inaccessible, or lacks the necessary execution permissions (e.g., on Linux/macOS, the driver file may not be executable).
154
+
155
+
156
+
### Possible Solutions
157
+
158
+
- Ensure the WebDriver version matches the browser version. For Chrome, check the browser version at `chrome://settings/help` and download the matching driver from [ChromeDriver Downloads](https://chromedriver.chromium.org/downloads).
159
+
- On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
160
+
- Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
161
+
145
162
## ElementNotVisibleException
146
163
147
164
This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible.
@@ -156,4 +173,4 @@ This can occur in several situations:
156
173
157
174
This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following:
158
175
using an explicit wait, or interacting with the page in such a way to make the element visible
Copy file name to clipboardExpand all lines: website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.pt-br.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,6 +142,23 @@ This usually occurs when the session has been deleted (e.g. `driver.quit()`) or
142
142
143
143
Check your script for instances of `driver.close()` and `driver.quit()`, and any other possible causes of closed tabs/browsers. It could be that you are locating an element before you should/can.
144
144
145
+
## SessionNotCreatedException
146
+
147
+
This exception occurs when the WebDriver is unable to create a new session for the browser. This often happens due to version mismatches, system-level restrictions, or configuration issues.
148
+
149
+
### Likely Cause
150
+
151
+
- The browser version and WebDriver version are incompatible (e.g., ChromeDriver v113 with Chrome v115).
152
+
- macOS privacy settings may block the WebDriver from running.
153
+
- The WebDriver binary is missing, inaccessible, or lacks the necessary execution permissions (e.g., on Linux/macOS, the driver file may not be executable).
154
+
155
+
156
+
### Possible Solutions
157
+
158
+
- Ensure the WebDriver version matches the browser version. For Chrome, check the browser version at `chrome://settings/help` and download the matching driver from [ChromeDriver Downloads](https://chromedriver.chromium.org/downloads).
159
+
- On macOS, go to **System Settings > Privacy & Security**, and allow the driver to run if blocked.
160
+
- Verify the driver binary is executable (`chmod +x /path/to/driver` on Linux/macOS).
161
+
145
162
## ElementNotVisibleException
146
163
147
164
This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible.
@@ -156,4 +173,4 @@ This can occur in several situations:
156
173
157
174
This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following:
158
175
using an explicit wait, or interacting with the page in such a way to make the element visible
0 commit comments