eos.contract doesn't work, account_missing error

eos : dawn4.2 scatter : 4.0.3

when I call eos.contract, it gives account_missing error. I think code is correct… and I set all scatter things correctly. (identity, key pair, account…) Is it just version missmatch problem? or should I modify the code?

code :

const eosOptions = {};
const eos = scatter.eos( network, Eos.Localnet, eosOptions );
scatter.getIdentity({ accounts:[network] }).then(id => {
  const account = id.accounts.find(account => account.blockchain === 'eos');
  const options = {
                          authorization: [
                              `${account.name}@${account.authority}`,
                          ]
                      };

  eos.contract(MY_CONTRACT).then(contract => {
      contract.myAction(...args, options);
  })
})

error :

{type: "account_missing", message: "Missing required accounts, repull the identity", code: 402, isError: true} code : 402 isError : true message : "Missing required accounts, repull the identity" type : "account_missing"

[alexpmorris]

It also took me a quite a bit of effort to solve this due to all the outdated examples.

As such, I just wanted to share what finally worked for me, for use with the jungle testnet. This example demonstrates multiple transfers wrapped into a single transaction.

However, issue still remains that you can’t access http from an https site. If anyone knows of an active https rpc-node for jungle testnet, please share! 😃

var network = {blockchain:'eos', protocol: "http", host: 'ayeaye.cypherglass.com', port:8888, chainId:'038f4b0fc8ff18a4f0842a8f0564611f6e96e8535901dd45e43ac8691a1c4dca'}

scatter.getIdentity({accounts:[network]}).then(identity=>{ 
  const account = identity.accounts.find(acc=>acc.blockchain==='eos'); 
  const eos = window.scatter.eos(network, Eos, {broadcast:true, chainId:'038f4b0fc8ff18a4f0842a8f0564611f6e96e8535901dd45e43ac8691a1c4dca'}, "http"); 
  const requiredFields = {accounts:[network]};
  eos.contract('eosio.token', {requiredFields}).then(contract => {
    contract.transaction(tx => {
      tx.transfer('abcabcabc123', 'abcabcabc321', '1.1234 EOS', '');
      tx.transfer('abcabcabc123', 'abcabcabc321', '1.4321 EOS', '');
    }).then(trx => { console.log("trx", trx); });
  });
});

[nsjames]

There’s two cases which could return this error.

The account specified is not attached to the network specified https://github.com/EOSEssentials/Scatter/blob/master/src/services/SignatureService.js#L62

The name@permission is incorrect or not included in the messages.authorization from the EOS transaction when collected. https://github.com/EOSEssentials/Scatter/blob/master/src/services/SignatureService.js#L72

payload.messages
    .map(message => message.authorization
        .map(auth => `${auth.actor}@${auth.permission}`))

It’s possible something has changed with the latest eosjs or EOSIO. I am pulling latest master and checking.