- the ISP alters ETag header for some reason.
- the SDK retries due to bad network connection and causes MD5 incorrectly computed. Is the network reliable?
- when uploading the file, someone overwrites the ETag value. Unlikely though, otherwise downloading this file in any ISP would have the same issue.
- some unknown bug in the SDK
Would you please get the file from the device and compute its MD5? It should match the value in S3.
Read full article from com.amazonaws.AmazonClientException: Unable to verify integrity of data download · Issue #62 · awslabs/aws-sdk-android-samples
No comments:
Post a Comment