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
Workaround is to launch Chrome with following flag (Windows example)
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-features=LockProfileCookieDatabase
For me this is okay because I do not use Chrome as my main browser; only to facilitate session cookies for my Node utilities via chrome-cookies-secure. But for someone using Chrome as their main browser, such disablement would obviously mean they are missing out on the security benefit that Google introduced in 114.
I'm getting this error on Windows 11 with Chrome 120.0.6099.130. Trying to copy the cookies file in explorer fails because file is open in Google Chrome
Chrome 114 introduces "Lock profile cookie files on disk" which breaks chrome-cookies-secure
[Error: SQLITE_CANTOPEN: unable to open database file Emitted 'error' event on Database instance at:]
{ errno: 14, code: 'SQLITE_CANTOPEN' }
The text was updated successfully, but these errors were encountered: