-
Notifications
You must be signed in to change notification settings - Fork 31
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
Uncaught TypeError: Cannot read property '0' of undefined #6
Comments
What version of Truffle are you using, can you post anything about how you are using this method? It's most likely caused by Truffle using decodeEvent with some inputs your feeding it. So it could just be your inputs, or something internally with Truffle, potentially due to a recent update (v3.3 Lemon) I doubt its ethjs-abi however, as we have not changed much in the past while. I'll ping tim. @tcoulter any thoughts? |
I am getting the same error, with the truffle-init-webpack project. Here's the steps I have taken on a clean environment: npm install -g truffle@beta open in chrome inkl Metamask Same happens on Firefox without MetaMask in the middle. I also think it is not really related to ethjs-abi, because as far as I can tell the function where it fails (decodeEvent(...)) has not changed since version 0.0.1. Haven't had the chance to dig deeper yet, any pointers would be helpful though. Thanks, |
I'm using the exact same method as @tomw1808 with Truffle beta. |
I am also getting the same error, with truffle init webpack project. |
I am also getting the same issue with the steps above. This has to do with whether or not I define an event parameter as indexed (removing it fixes the issue). |
Will take a look at this, thanks, I'll talk with Tim, he didn't seemed too bothered by this before.
…Sent from my iPhone
On Jul 13, 2017, at 3:40 PM, Ericxgao ***@***.***> wrote:
I am also getting the same issue with the steps above. This has to do with whether or not I define an event parameter as indexed (removing it fixes the issue).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I haven't been able to reproduce the issue with the steps provided. @tomw1808 You gave these steps:
You didn't list migrating (i.e., deploying) your contracts. Did you perform that step before continuing? Can you tell me what operating system you guys are using? So far it looks like Windows. |
Yes, Windows 8.1 64-bit |
I've successfully reproduced, but only on Windows. Diagnosing. |
I've found the culprit, though I don't understand it. TL;DR: Background:If you look here, SolutionI'll bump a version of Obligatory aside: Note that we're moving away from |
This has been fixed. You should now be able to perform the following on Windows with no issue:
You'll be able to use the example application as expected. Cheers! @SilentCicero, you can close this issue. |
Hey @tcoulter sorry the late reply and thanks for fixing it. OT question: Moving away from truffle-init-webpack and into the truffle boxes is understandable. They are great. But will there be a box that starts with vanilla JS and just implements a basic build environment for javascript? Webpack was pretty convenient to have just that without the hassle of scaffolding for a quick vanilla js Dapp-project for prototyping. Any recommendations on that side? |
Issue Type
Description
On a private-network on port 8545 using testrpc and MetaMask when I send coins to another account I get this error
Steps to reproduce
On Windows
Prompt1
truffle.cmd init webpack
Prompt2
testrpc
Prompt1
truffle.cmd compile
truffle.cmd migrate
npm run dev
Go to localhost:8080
Versions
The text was updated successfully, but these errors were encountered: