Get Easy Save from the Unity Asset StoreUnity 2020.3.11f1
Easysave3 3.4.0
I found the following errors from some gamers.
[CryptographicException: Could not decrypt file. Please ensure that you are using the same password used to encrypt the file.]
Of course, there are many gamers who haven't changed their passwords and just make the following errors as soon as they start the game.
Is there a way to solve this?
I understand that if you unlock the encryption in the setting because you want to avoid this error, the save file will fail.
You can't do that because it's already a game in service.
Please tell me how.
Quite a few gamers are suffering from this problem to be called a few problems.
Error: cryptographicexception: could not decrypt file
Re: Error: cryptographicexception: could not decrypt file
Hi there,
This error will occur for the following reasons:
1. A different password is being used to the one used to encrypt it.
2. Parts of the code are using encryption but other parts are not, meaning unencrypted data is trying to be loaded as if it’s encrypted.
3. The data has become corrupt due to a hardware issue.
4. The data has become corrupt due to an external app accessing and modifying it (for example, third-party cloud or anti-virus software).
5. The data has become corrupt because the user had tampered with it.
6. A different exception occurred in a previous session which led to incomplete data. For example an IOException due to lack of space.
3 to 6 are out of your control and occur on any app which stores data.
It wouldn’t be possible to know without being able to replicate the issue. However, it’s likely that it could be for a different reason for each user.
Generally to mitigate the issues which are out of your control, you should use backups and roll back to a previous save file when the data becomes corrupted:
https://docs.moodkie.com/easy-save-3/es ... s/backups/
All the best,
Joel
This error will occur for the following reasons:
1. A different password is being used to the one used to encrypt it.
2. Parts of the code are using encryption but other parts are not, meaning unencrypted data is trying to be loaded as if it’s encrypted.
3. The data has become corrupt due to a hardware issue.
4. The data has become corrupt due to an external app accessing and modifying it (for example, third-party cloud or anti-virus software).
5. The data has become corrupt because the user had tampered with it.
6. A different exception occurred in a previous session which led to incomplete data. For example an IOException due to lack of space.
3 to 6 are out of your control and occur on any app which stores data.
It wouldn’t be possible to know without being able to replicate the issue. However, it’s likely that it could be for a different reason for each user.
Generally to mitigate the issues which are out of your control, you should use backups and roll back to a previous save file when the data becomes corrupted:
https://docs.moodkie.com/easy-save-3/es ... s/backups/
All the best,
Joel