-
Notifications
You must be signed in to change notification settings - Fork 2.3k
"contract binary not set. Can't deploy new instance." when deploying simple contract #231
Comments
btw I ended up not deploying this contract and just imported it for use in other contracts, but will just log the possible bug here |
Your contract is an abstract contract and will therefore have no binary. On Aug 9, 2016 7:01 AM, "zweicoder" notifications@github.com wrote:
|
The TestRPC's filter changes is a separate issue I've seen as well. On Aug 9, 2016 7:01 AM, "zweicoder" notifications@github.com wrote:
|
ok thanks for the info! |
I'm going to close this one for housekeeping purposes. If you run into any more issues please open a new ticket! |
I just had this error too, @tcoulter. I wouldn't doubt I've got an abstract contract on my hands. Any idea if there's a way to get an error saying which method isn't implemented? |
During the last 2 weeks I have come across this error twice, and both times resolved it by doing a Google search and this issue comes up with the answer:
Maybe the error message should be updated to give a hint towards that. |
I got this error with Truffle 3.1.1 after running The error message was coming from The error stopped after running |
If you have one function that is an abstract function in your contract.
The whole contract is compiled as an abstract contract, so you will get this error message. Then your contract will compile. |
Similar issue migrating ERC20 token standard contract.
Yes, this an "abstract" contract as the methods are not implemented. I have attempted to add my Has anyone had success migrating the ERC20 contract? |
I get this error after updating a contract and running tests. I need to remove the build folder and recompile the contracts and then run the tests to fix. |
This is still happening intermittently - not sure what causes it. All methods are implemented and all constructors are properly called. |
Ok the issue for me was that I had an interface defined in a contract that had the same name as one of my contracts. The interface was being compiled and I expected the contract to be compiled. I've suffixed all my interfaces with |
@pizza-r0b sounds like this can stay closed, as a duplicate of #1087 Thanks for sharing findings of your investigation! |
This interface throws
contract binary not set. Can't deploy new instance.
when deployed withdeployer.deploy(JudgeSubscriber);
More info from @elenadimitrova from Gitter who reproduced it:
The text was updated successfully, but these errors were encountered: