[BUG]: Selenium fails to use existing Chrome user profile for automated browser session

[doncorleon73]

Describe the bug

When using Selenium with ChromeDriver to automate navigation on LinkedIn, we are experiencing difficulties using the existing Chrome user profile.

Steps to reproduce

Current Behavior

• When initializing the browser with Selenium, a new Chrome window opens
• This new window is not logged into the LinkedIn account
• The existing user profile is not loaded correctly

Environment

• Operating System: Windows 11
• Chrome Version: 131.0.6778.205
• ChromeDriver Version: 131.0.6778.204
• Selenium Version: 4.9.1
• Python Version: 3.12.3

Steps to Reproduce

1. Use Selenium to initialize a new Chrome browser
2. Attempt to use the existing Chrome user profile
3. Observe the opening of a new, unconnected browser window

Expected behavior

When initializing the browser with Selenium, the script should open an existing Chrome browser session The browser should use the default Chrome profile located at C:\Users\XXXX\AppData\Local\Google\Chrome\User Data The LinkedIn session should be already logged in, using the existing authenticated browser profile The browser should navigate directly to the specified URL (LinkedIn jobs page) using the existing session

Actual behavior

Selenium opens a brand new Chrome browser window The new browser window is not logged into LinkedIn The existing Chrome profile is not used A separate, unauthenticated browser session is created The script fails to leverage the existing browser session and authentication

Branch

None

Branch name

No response

Python version

3.12.3

LLM Used

Claude

Model used

claude-3-opus-20240229

Additional context

No response