[Ethereum] How deploy a smart contract with meteor and metamask

contract-deploymentdapp-developmentmetamaskmeteor

I will deploy a smart contract with meteor and matamask.
My code in main.js :

var inactivityTime = 1000;
var continuityContract = web3.eth.contract(Continuity.abi);
var continuity = continuityContract.new(
   inactivityTime,
   {
     from: web3.eth.accounts[0],
     data: Continuity.bytecode,
     gas: 4700000
   }, function (e, contract){
    console.log(e, contract);
    if (typeof contract.address !== 'undefined') {
         console.log('Contract mined! address: ' + contract.address + ' transactionHash: ' + contract.transactionHash);
    }
 })

but I have this error

Uncaught Error: The MetaMask Web3 object does not support synchronous
methods like eth_uninstallFilter without a callback parameter.

Any idea ?

Code is on github: https://github.com/n1c01a5/etherlife.co

Best Answer

There is a great series of tutorial I followed to deploy a meteor Dapp, that you can find here.

It's fairly recent, and when I had problems I left a comment and the author answered personally and helped me fix my mistakes. You should check it out.

Related Solutions

[Ethereum] How to store asynchronous callback values in an variable

You probably does not understant the asynchronous nature of your call. In the following example, Line A is executed after Line B. Thats why in Line B you will see undefined:

var num;
myContract.numIssuer (function (err, res) {
  num = res; // Line A
});
console.log ("Num is: " + num); // Line B

You need to put received value into the list inside callback, not after the call like this:

myContract.numIssuer (function (err, res) {
  if (!err) displayInList (res);
});

[Ethereum] Getting Uncaught Error: new BigNumber() not a number: [object Object]

We get these occasionally when we make a change to MyEtherWallet, and we don't use Solidity or web3. It's a JS thing in the BigNumber.js library that web3 also uses.

Somewhere you have something that you think is a number but it's actually a string, null, array, object, or something else. This was some code for sending a signed TX via the offline tab. The error in our case was BigNumber Error: new BigNumber() not a number: 0x. And the fix:

[before] $scope.tx.value = etherUnits.toEther('0x'+eTx.value.toString('hex'),'wei');
[after] $scope.tx.value = eTx.value.toString('hex')!='' ? etherUnits.toEther('0x'+eTx.value.toString('hex'),'wei') : 0;

So before we were just like "take that value and do stuff with it". The fix was "if this value isn't empty, then do stuff with it, otherwise return 0.

So. Things to try...

console.log your variables before AND after, error or no error, and also log their types: console.log(typeof myContract)
Make sure that you are catching any empty or null values and either retuning a number (e.g. 0), or not continuing on
Make sure you are passing what you think you are passing. For example, are you really passing the address, or fromaddress, or contract.address, or something else?
In your case, it's saying [Object object], which makes me think something is an object. In that case do console.log( JSON.stringify(myContract) ) as well so you can actually see what it is.
Anything that you log that returns something funky like Object { s: 1, e: 0, c: Array1 }, you need to either
- toString to get it's value as a decimal string
- toNumber to approximate it as a JS number.
- (That object is the object from BigNumber.js)

If you do all of those things, you will discover the spot where you thought something was something, but it was actually somethingElse. Then it's an easy fix.

Best Answer

Related Solutions

[Ethereum] How to store asynchronous callback values in an variable

[Ethereum] Getting Uncaught Error: new BigNumber() not a number: [object Object]

Related Topic