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.