Replies: 4 comments 4 replies
-
Hi @PhrackNZ It seems that you've encountered an issue after upgrading from version 5.7 to version 6.3 of The error message indicates that there is an "invalid value for value.removed" and it specifically mentions that the value is null. This error is raised because the To resolve this issue, you can try explicitly setting the removed property to const logs = await provider.getLogs({
fromBlock: 20412500,
toBlock: 20412600,
topics: [ethers.utils.id('Transfer(address,address,uint256)')],
removed: false // Add this line to explicitly set the 'removed' property
}); By explicitly setting If the issue persists or if you need further assistance, please provide additional details. This information will help in diagnosing the issue more accurately. Hope this helps! Let me know if you have any other questions. Best regards, |
Beta Was this translation helpful? Give feedback.
-
Actually, disregard my previous answer. I can reproduce the error on my end and had misunderstood your error. It has been referenced here: #3959 This will be fixed by this commit: 4e478e6 |
Beta Was this translation helpful? Give feedback.
-
I temporarily fixed it by replacing line 86 in
As you can see by the following successful execution:
|
Beta Was this translation helpful? Give feedback.
-
I'm still having a similar issue with v6.9.2.
|
Beta Was this translation helpful? Give feedback.
-
Just upgraded to v6.3 from 5.7 and suddenly getting this problem when trying to use getLogs. Not sure if it is something I missed in the changes or an ethers issue.
Error: invalid value for value.removed (invalid boolean; undefined (argument="value", value=null, code=INVALID_ARGUMENT, version=6.3.0))
Beta Was this translation helpful? Give feedback.
All reactions