AlexPaiva
commented
8 months ago Fixed by pip install --upgrade protobuf as for some reason it was an older version and when installing the protoc compiler to transform .proto into .py you need to download the latest release from here: https://github.com/protocolbuffers/protobuf/releases
Protobuf replies have extra bytes added/messed with so the reply is no longer valid to be decoded with the expected .proto file decoder, works fine when used with httpx or requests on python.
I think it's not related to noble-tls itself but the base tls client it uses. I have created https://github.com/bogdanfinn/tls-client/issues/99 for reference. Creating here aswell as I am unsure if it's related to tls-client or noble-tls and so that you are aware aswell.