Chris

@sbking could you set up a small repository with some code so I can debug this issue on my side? No sensitive data or secret keys, just the code you...

Hi @sbking good that you found a workaround. I will investigate this further. I assume the `signer.sign()` somehow changes the body and you avoid that by cloning the request and...

Hey @sbking I'm planning to give this issue another go. I want to try your solution and copy the signed headers instead of using the `signedRequest.headers` like I do now....

@sbking I've released v4.1.0 which only copies the headers to the request. Could you try if that works for you?

@florianbepunkt thank you very much for these links, they have finally put me on the right track. I think there are two different issues here: ### 1. Fetching with a...

> Interestingly enough, this works without specifying duplex: "half" in the request. Not sure why. In which environment / Node.js version did you try it? Maybe `Request` or `fetch` was...

@florianbepunkt it's not working for me either, and I'm trying to figure out the issue. I'll let you know when I know more.

Hey @florianbepunkt I think I finally managed to fix it. I now always create a `Request` object based on the original `input` and `init` objects, that means whatever options is...

Hey @sbking and @florianbepunkt I released v4.2.0 which should close finally this issue 🙏 Thanks to @florianbepunkt I identified the root cause: when provided with a `Request` object like `await...

I didn't check it carefully, it's not a typo but the examples are mixed up: I now switched the code examples, I think that's correct now.