itscynxx
commented
1 year ago This has been an issue for a long while, where resetting config simply doesn't do anything, seeming to be because it just writes {} to the config file which also invalidates it (this may not be the exact cause but, regardless, it does not work)
As Lumi mentioned, this simply makes it delete the viper.json when detected as invalid. Deleting it won't affect the end user's device, as it would be reset normally and it being deleted simply makes viper hard reset it. This may require things such as an update to the version number or possibly packaging the code for release, however this is still an issue that should be actively worked on as it affects plenty of end users while trying to help them, and end users shouldn't be required to find the .json file themselves and delete it, as the point of a manager is to mitigate the effort put in by an end user.
We have tested this on Windows as well as Silverblue Linux, however it should realistically work anywhere that viper already works on.
0neGal
LumiKattlin
On restart, if the json file was broken supposedly would try to repair but it wouldn't work, it would keep repairing but failing. This should fix it by deleting the json file and creating a new one at the start with the correct settings (hopefully)