v126.x (Chrome bootstrap) unable to load cookies from prior version (Alloy bootstrap) #4847

Activity

1. amaitland

   changed the title [-]v126.x seems to trash the cookies from prior versions[/-] [+]v126.x unable to load cookies from prior version[/+] on Jun 24, 2024
2. amaitland

   added

   upstreamThese issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.

   on Jun 24, 2024
3. amaitland commented on Jun 24, 2024

   

   amaitland

   on Jun 24, 2024

   Member

   More actions

   Thanks for the detailed testing 👍 It's important to remember that CefSharp is just a wrapper around the Chromium Embedded Framework(CEF).

   Try switching back to the Alloy bootstrap to see if that makes a difference. Refer to #4835 (comment)

   Ultimately this will need to be raised at https://github.com/chromiumembedded/cef/issues
4. EamonHetherton commented on Jun 24, 2024

   

   EamonHetherton

   on Jun 24, 2024

   Last edited by EamonHetherton

   Author

   More actions

   Thanks for the prompt reply, settings.ChromeRuntime = false; does appear to fix the issue with cookies still being loadable after the update. I'll try to dig deeper into the root cause.
5. EugeneSunrise commented on Jun 24, 2024

   

   EugeneSunrise

   on Jun 24, 2024

   More actions

   Thanks for the prompt reply, settings.ChromeRuntime = false; does appear to fix the issue with cookies still being loadable after the update. I'll try to dig deeper into the root cause.

   I had a similar problem, the point is that when we use chrome bootstrap(ChromeRuntume = true, since 125 ver.) cookies are encrypted with a key that is stored in the Local State file, but if we use alloy bootstrap cookies are encrypted with a key from LocalPrefs.json

   👍React with 👍1Reacted by Eamon Hetherton
6. amaitland commented on Jun 24, 2024

   

   amaitland

   on Jun 24, 2024

   Member

   More actions

   Thanks for the prompt reply, settings.ChromeRuntime = false; does appear to fix the issue with cookies still being loadable after the update. I'll try to dig deeper into the root cause.

   Please raise an issue on the https://github.com/chromiumembedded/cef/issues (post a link back here for reference).

   We'll need to see if CEF can handle this case gracefully.
7. amaitland

   changed the title [-]v126.x unable to load cookies from prior version[/-] [+]v126.x (Chrome bootstrap) unable to load cookies from prior version (Alloy bootstrap)[/+] on Jun 24, 2024
8. EamonHetherton commented on Jun 24, 2024

   

   EamonHetherton

   on Jun 24, 2024

   Author

   More actions

   chromiumembedded/cef#3721
9. EamonHetherton commented on Jun 24, 2024

   

   EamonHetherton

   on Jun 24, 2024

   Last edited by EamonHetherton

   Author

   More actions

   We don't plan to migrate cache directories automatically
   chromiumembedded/cef#3721 (comment)
   :(

   I thought about trying to auto detect the first run with the Chrome bootstrap and initialise the Alloy bootstrap first and extract all the cookies, then load Chrome bootstrap and insert the cookies but can only initialise CEF once per process so that becomes significantly more difficult
10. EamonHetherton commented on Jun 25, 2024

    

    EamonHetherton

    on Jun 25, 2024

    Last edited by EamonHetherton

    Author

    More actions

    some success: chromiumembedded/cef#3721 (comment)

    Still not sure what to use to detect "first run" of Chrome bootstrap (probably the existence of LocalPrefs.json and not Local State file at this stage), but I think following the steps outlined in that link might work for me. Will also need to consider what other files/folders should be cleaned up as part of the Alloy->Chrome bootstrap migration.

    Any thoughts on what else may need migrating?
11. EamonHetherton commented on Jun 25, 2024

    

    EamonHetherton

    on Jun 25, 2024

    Author

    More actions

    Work in progress migration, works for me YMMV :)

    public static class Alloy_To_Chrome_Migration
    {
        private static readonly string[] FoldersToMigrate = ["Cache", "Code Cache", "DawnGraphiteCache", "DawnWebGPUCache", "GPUCache", "Local Storage", "Network", "Session Storage", "Shared Dictionary"];
        private static readonly string[] FilesToMigrate = ["LOCK", "LOG", "Visited Links"];
        private const string AlloyStateFilename = "LocalPrefs.json";
        private const string ChromeStateFileName = "Local State";
        public static void Execute(CefSettings settings)
        {
            var cache_path = settings.CachePath;
            try
            {
                string alloyStateFile = Path.Combine(cache_path, AlloyStateFilename);
                string chromeStateFile = Path.Combine(cache_path, ChromeStateFileName);
                if (settings.ChromeRuntime && File.Exists(alloyStateFile) && !File.Exists(chromeStateFile))
                {
                    File.Move(alloyStateFile, chromeStateFile);
    
                    var defaultDir = Path.Combine(cache_path, "Default");
                    Directory.CreateDirectory(defaultDir);
    
                    foreach (var migrationFolderName in FoldersToMigrate)
                    {
                        var migrationFolder = Path.Combine(cache_path, migrationFolderName);
                        if (Directory.Exists(migrationFolder))
                        {
                            Directory.Move(migrationFolder, Path.Combine(defaultDir, migrationFolderName));
                        }
                    }
                    foreach (var migrationFileName in FilesToMigrate)
                    {
                        var migrationFile = Path.Combine(cache_path, migrationFileName);
                        if (File.Exists(migrationFile))
                        {
                            File.Move(migrationFile, Path.Combine(defaultDir, migrationFileName));
                        }
                    }
                }
            }
            catch (Exception)
            {
            }
        }
    }
    

    👍React with 👍2Reacted by Alex Maitland and Yegor Chasnovskiy
12. amaitland

    added

    faq-able!

    on Oct 26, 2024
13. amaitland commented on Oct 26, 2024

    

    amaitland

    on Oct 26, 2024

    Member

    More actions

    We don't plan to migrate cache directories automatically. CEF doesn't know what Profile-specific directory you were using previously, and not all files/directories are applicable between Chrome and Alloy bootstraps.

    chromiumembedded/cef#3721 (comment)

    As CEF isn't going to support automatic migration, it'll be up to users to manually migrate if required.
14. amaitland

    closed this as not plannedon Oct 26, 2024