There was an issue with it that would cause improper loading of the settings file in v2.2.8. There is a chance that the file was corrupted in the process. As a result, we've added a couple of checks to prevent this from happening and help with recovery if it does.
If you were affected, please see this for help and if reach out to us if you need extra support.
Changed files in this update