Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web3swift.Web3Error error 4 for get balance #77

Closed
Mahdimm opened this issue Oct 29, 2018 · 5 comments
Closed

web3swift.Web3Error error 4 for get balance #77

Mahdimm opened this issue Oct 29, 2018 · 5 comments

Comments

@Mahdimm
Copy link

Mahdimm commented Oct 29, 2018

Hi @shamatar
I used the same exact code in one of my projects to get Balance and it works well but now I will get error with same situation, this is error code when I try to get balance:

The operation couldn’t be completed. (web3swift.Web3Error error 4.)
Link Here

@shamatar
Copy link
Contributor

shamatar commented Oct 29, 2018 via email

@MrShafiee
Copy link

Hi @shamatar ,
You need more screenshots from which part of code?
You can see complete error in this screen shot: image

and I think problem is here in this image, our data is 0 byte! but the network request has successful response and get correct balance value, and when it wants map to JSONRPCresponseBatch this error occur, thus we get error for typeMissMatch here in map function.

Do you need more screenshots? if yes from which part of code?
Thanks

@MrShafiee
Copy link

Hi @shamatar ,
Did you find any problem or you need more data?

@shamatar
Copy link
Contributor

shamatar commented Nov 3, 2018 via email

@Mahdimm
Copy link
Author

Mahdimm commented Nov 5, 2018

Hi @shamatar
It was related to response from node, in this project we used Quorum that use older version of Ethereum. for this reason node return Array instead of Dictionary and we will get error while parsing response.

thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants