John L.

Quick update; still working with service team to make the type change in the model.

Hi @luong-komorebi - thanks for reporting. While we further look into it, can you share your SDK minimal repro code with Next.js? Here's my quick repro attempt with `3.629.0` and...

Hi all - checking in here. Reading through the comments, it sounds like the root cause was due to a change made in Next.js and available workaround is mentioned [here](https://github.com/aws/aws-sdk-js-v3/issues/6411#issuecomment-2323899011)....

@luskin - thanks for checking in. Are you reporting the same issue as the original post? It seems like what you shared appears to be different issue? For the build...

Hi @sdeneen - thanks for reaching out and your patience. I investigated this behavior and here's what I found: 1. Node.js Execution: - Cloned and set up your repo -...

@sdeneen - thanks for the additional info! I'd like to address and verify a few things: >I had to update the CORS policy on the S3 bucket to allow localhost...

>Yep! I locally added some logging in the SDK to verify the error being thrown is the checksum mismatch, Can you share the logs? It's strange that I'm not seeing...

>Are you able to reproduce the error using the branch I linked? I'm not able to reproduce the error mimicking the exact code from your `checksum-mismatch-bug-test` branch. See screenshot below....

Sorry for the late reply. We've had no luck in successfully reproducing this on our end. >The other thing is the S3 object uploaded in the S3 bucket my branch...

Hi @sdeneen - more update here. I further looked into this with my colleague and here's what we found. Previously, I downloaded your `uncompressed.txt.br` from your repo, uploaded to my...