We have a Unit Test for that (we have developed our own FNC client using API of FNC 2017 R3).It downloads a file and in the definition of a MultiPlatform Update used for this test we have set SHA1 to a wrong value.During the Unit Test we first check ...
We are using sha1 signatures since years. It works, that means:when I corrupt a file on the server and download it, FNC-SDK detects that the SHA1 does not match and signals an exception.When I download the uncorrupted file it works in 99.9%But we see...