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

abi: attempting to unmarshal an empty string while arguments are expected #29642

Open
mjaniko opened this issue Apr 24, 2024 · 1 comment
Open
Labels

Comments

@mjaniko
Copy link

mjaniko commented Apr 24, 2024

System information

Geth version: v1.13.15
CL client & version: e.g. lighthouse/nimbus/prysm@v1.0.0
OS & Version: OSX 14.4.1 (23E224)
Commit hash : (if develop)

Expected behaviour

Since migrating my go-etherum from v1.10.22 to v1.13.15 my smart contracts started firing
abi: attempting to unmarshal an empty string while arguments are expected.
Which i didn't expect to be.

I have been testing multiple versions of go-etherum. I was succesfully able to migrate on v1.11.6 but moving forward with v1.13.0 started to introduce issues.

Steps to reproduce the behaviour

I have tried to regenerate go smartcontract with abi and bin but still running with same issue.
contact is build on solidity ^0.5.0;

@luopiao
Copy link

luopiao commented Apr 30, 2024

change your version,for example:
replace github.com/ethereum/go-ethereum v1.13.14 => github.com/ethereum/go-ethereum v1.12.2

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

No branches or pull requests

2 participants