Found an issue, after calling FileFormatInspector.DetermineFileFormat, the stream position is set to the byte position it read last during inspecting the file stream. This corrupts the passed stream, if the passed stream is to be uploaded to the file server the file is corrupted now. This is because the header bytes are missing because stream never reset back to its original position. As an API Consumer, I expect the stream to be in its original position which is Zero.
Found an issue, after calling FileFormatInspector.DetermineFileFormat, the stream position is set to the byte position it read last during inspecting the file stream. This corrupts the passed stream, if the passed stream is to be uploaded to the file server the file is corrupted now. This is because the header bytes are missing because stream never reset back to its original position. As an API Consumer, I expect the stream to be in its original position which is Zero.