XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed after #218

[onhate]

I'm getting XAmzContentSHA256Mismatch error on next bucket deployment lambda stage.

I've traced to the 4.0.0-beta.31 release, it works on 4.0.0-beta.30, so definitely #218 is the root cause

https://github.com/jetbridge/cdk-nextjs/releases/tag/v4.0.0-beta.31

[bestickley]

@jadenv, any ideas about this? Have you ever experienced this?

[jadenv]

Interesting, we have not come across this error in any of our repo's deployments.

Before the switch, we experienced random asset upload failures a couple of times a week, which were resolved with a manual re-deploy. However, since making the switch to lib-storage, we haven't encountered a single assets deployment issue yet.

[m-kemarskyi]

@onhate I have the same problem with the version 4.1.1. By any chance, do you have any updates on it?
Maybe the issue was different and you managed to solve it? Or you simply downgraded to the version 4.0.0-beta.30?

[m-kemarskyi]

@jadenv Looks like the use of lib-storage Upload instead of PutObject is definitely the cause - I experience exactly the same behaviour as @onhate, and this @aws-sdk/lib-storage open issue seems to be the root cause.

Probably worth considering reverting this change until the issue is resolved on the AWS SDK side?