AllanZhengYP

Hi @mjgp2 Can you also share the content of `data` when error code cannot be parsed? It'll be helpful to use to roll out a correct fix.

Removing the needs-review because we know it requires a better error message. But it's not blocking customer from making request to AWS services. We will implement a fix soon.

Replaced by https://github.com/aws-amplify/amplify-js/pull/10553

@merceyz Thank you for the response. I tested on v16.14 but still got no luck: ```console System: OS: macOS 12.2.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Binaries:...

@merceyz The issue still exists, can you take another look?

This feature is implemented in AWS CLI as a customization: https://github.com/aws/aws-cli/pull/4141

Thank you for the advice! @seriousme We are currently weigh in the options including WASM, ASM.js, and pure JS with WebCrypto. Currently one of the obstacle is that WASM seems...

@jekh Thanks a lot for pointing this out! It's a miss on our side. I will address them a separate PR.

Hi @deweve Can you confrim whether the issue persists on the latest version `3.42.0`?

Hi @ffxsam Thank you for reporting this. The root cause of the problem is that the `Error` is not defined [here](https://github.com/aws/aws-sdk-js-v3/blob/25cb359e69966c549eb505956c2aeee809819245/clients/client-s3-control/protocols/Aws_restXml.ts#L6789). We can potentially use optional chaining to make it...