I'm using CEF via the downstream project CefSharp which had previously used the Alloy bootstrap but is switching to the Chrome bootstrap by default in v126. As a result of this, cookies that existed prior to switching are no longer available.
To Reproduce
Steps to reproduce the behavior:
- Initialize CEF using Alloy bootstrap with a clean cache_path
- Create a cookie (or visit site that sets a cookie)
- Restart CEF now using Chrome bootstrap with same cache_path
- No cookies exist
Expected behavior
Either cookies available by default after switching to use Chrome bootstrap or an option provided to migrate them from Alloy to Chrome.
Versions:
- OS: Windows 11
- CEF Version: 126.2.7
Additional context
(cefsharp/CefSharp#4847)
It was suggested by another user on the CefSharp issue that it is due to the Chrome bootstrap using an encryption key that is stored in the Local State file, but the Alloy bootstrap uses a key from LocalPrefs.json
I'm using CEF via the downstream project CefSharp which had previously used the Alloy bootstrap but is switching to the Chrome bootstrap by default in v126. As a result of this, cookies that existed prior to switching are no longer available.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either cookies available by default after switching to use Chrome bootstrap or an option provided to migrate them from Alloy to Chrome.
Versions:
Additional context
(cefsharp/CefSharp#4847)
It was suggested by another user on the CefSharp issue that it is due to the Chrome bootstrap using an encryption key that is stored in the Local State file, but the Alloy bootstrap uses a key from LocalPrefs.json