GoogleChromeLabs / GoogleChromeLabs/chrome-for-testing
Cookies dissapear when automation
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 159
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 3
Description
> [!IMPORTANT]
> **This issue tracker tracks bugs with [the Chrome for Testing availability dashboard](https://googlechromelabs.github.io/chrome-for-testing/) and [its API](https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints).**
>
> - Are you reporting a bug that reproduces in Chrome for Testing but not in Chrome? File it here: https://goo.gle/cftbug
> - Are you reporting a bug in Chrome? File it here: https://crbug.com/new
**Describe the bug**
When I launch with selenium any chrome profile the cookies dissapear, even chrome profile logs out.
**To reproduce**
Steps to reproduce the behavior: Use selenium python to launch specified chrome profile
**Expected behavior**
I thought they wont dissapear, how can I make them stay?
**P.S**
switched to chrome for testing, now this [19804:19988:0830/015319.710:ERROR:components\os_crypt\sync\os_crypt_win.cc:105] Failed to decrypt: The parameter is incorrect. (0x57)
spammed my console
Contributor guide
Research direction
Start by reproducing the report with Selenium Python and a specified Chrome profile, comparing regular Chrome with Chrome for Testing. Check whether the reported os_crypt_win.cc decryption error appears; done would require a confirmed repository-side cause and a documented reproduction or fix, but no source file or test is identified here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100