sebdelsol

Please check [**this potentially better solution**](https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/693#issuecomment-1176409742).

You're supposed to search the existing issues before raising a new one... Anyway, please [**check this answer**](https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/639#issuecomment-1133890051). Thanks for closing this issue.

Did you properly import undetected-chromedriver from selenium-wire ? ```python3 # import undetected_chromedriver as uc import seleniumwire.undetected_chromedriver as uc ``` EDIT : please close this issue, _it has nothing to do...

I don't think it has anything to do with v103. Correlation is not causation. You're playing [**the headless-cat-n-mouse game**](https://github.com/paulirish/headless-cat-n-mouse) and now you've lost. I don't think it's a game worth...

Run : ```python3 import undetected_chromedriver as uc print(uc.Patcher.data_path) ``` And check you have the right permissions for the given folder.

* You don't need to manually open the Chrome process, _undetected-chromedriver_ does that for you. And the Chrome process is detached which is better for avoiding detection. * Only `'prefs'`...

Are you sure installing a very old version is the solution ? This one will be easily detected.

undetected-chromedriver launches a Chrome with a blank profile inherited from the master profile where notifications are usually blocked. So you can either: * Copy a profile where notifications are enabled...

The notifications option works for me, but I use a forked undetected-chromedriver that fixes some bugs with the `prefs` experimental options (and add some basic headless evasions btw), please [**check...

I concur, this is a duplicate. [Here are the only workarounds at the moment](https://github.com/ultrafunkamsterdam/undetected-chromedriver/issues/694#issuecomment-1165539116).