hedera-sdk-js: WebChannel.decodeUnaryResponse - "unexpectedly received no response"

Description

Executing a fileCreate or a cryptoGetBalance grpc service call returns no HTTP response.

It might be that other Executables are affected.

Note: We came across this issue while running our Strato tests base against hedera-sdk v2.12.0

Steps to reproduce

Bundle the sdk and deploy it to a webpage
In the same JS context, create either a FileCreateTransaction or an AccountBalanceQuery and try issuing it through the SDK
Inspect network operations to see the lacking of responses

Additional context

Hedera network

testnet

Version

2.12.0

Operating system

Linux

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 18 (9 by maintainers)

Most upvoted comments

Fixed: https://github.com/hashgraph/hedera-sdk-js/commit/bc2592b497d97c6cbccee5a458665fb278933d73 Can confirm our browser tests were now able to catch the original error of having HashgraphProto in the URL.

janaakhterov on Apr 27, 2022

I can expand on this - we have encountered this issue heavily when large projects are using HashConnect. I have talked to @gregscullard about it a bit, but it seems as though when the network is under load this error happens.

We have experienced it across all sorts of transactions on both testnet and mainnet - SmartContractExecute, TokenAssociate, Transfer, TokenMint, etc.

The weird part is that sometimes the transaction actually goes through, but then you get an error. This leaves us in a strange position.

It is a very large concern for us and many others.

Some screenshots:

teacoat on Apr 11, 2022

Hey, I’m not really sure where to begin with this issue, but it seems v2.12.0 had a bunch of silly mistakes which have now been fixed and released in https://github.com/hashgraph/hedera-sdk-js/releases/tag/v2.12.1 Can you attempt to rerun the tests using the updated version. If you’re still getting errors then further investigation will be needed.

Note: I tried cloning the repo you mentioned above and running the tests, but they seem to pass with 2.7.0, 2.12.0, and 2.12.1. Although maybe I’m just not running tests correct and/or looking at the correct thing. I ran npm run test:browser after updating .env.

janaakhterov on Apr 8, 2022