I received reports from players that their save file is corrupted, and I found one of the save file is full of zeros instead of normal json format.
There are currently two save slots, one is normal and one is auto save, the auto save appears to be fine.
The attached zip file contains the save file with all zeros and the auto save file that is normal.
This is usually always because an anti-virus has quarantined the file before a chance is given for the data to be written to it (usually this will also come with a Shared access exception). In this case the user would need to add an exception to their anti-virus for their file as you don't have control over what the anti-virus does as a developer.
However, in your case as you're using async code I would double check that you're only calling Easy Save from one thread at a time, as not doing so can cause a Shared access exception which will cause the above issue. I also recommend checking your error logs for exceptions.
In most cases it's not necessary to call StoreCachedFile asynchronously as it's usually quite a cheap operation unless you're saving things such as Textures or Meshes by value.
This is usually always because an anti-virus has quarantined the file before a chance is given for the data to be written to it (usually this will also come with a Shared access exception). In this case the user would need to add an exception to their anti-virus for their file as you don't have control over what the anti-virus does as a developer.
However, in your case as you're using async code I would double check that you're only calling Easy Save from one thread at a time, as not doing so can cause a Shared access exception which will cause the above issue. I also recommend checking your error logs for exceptions.
In most cases it's not necessary to call StoreCachedFile asynchronously as it's usually quite a cheap operation unless you're saving things such as Textures or Meshes by value.
All the best,
Joel
Thanks! I will inform my players and check my code again.