destructuring assignment

the reason is that the table abi may cannot provide the correct primary key of the table

1. provide ability to test node's connection
2. provide ability to test node's http-plugin
3. provide reliable nodes list
4. switch nodes automatically when a problem occurs

1. persistence
2. ordered
3. lazy loading
4. Support roaming

desc

In the case where scatter is normally injected, no scatter is found and an error message pops up.

env

version: 1.3.0-beta
chrome 70

phenomenon

• After one occurrence, it will be encountered every time.
• It seems to be strongly associated with a specific DAPP on a specific device.
• Scatter is actually loaded normally.
• The problem disappears after clearing the local storage.
• When the problem occurs, scatter seems to be frozen.

possible reasons

• error in the logic that uses local storage.
• error in the process of checking scatter.
• error in the handling of the chain's config. e.g. a wrong chain-id set.

1. listening specific account-actions and send notification to application layer.
2. quick response
3. error check
4. avoid replay

There is a problem with the judgment logic:

let maxActionInd = acts.length === 0 ? pos : acts[acts.length - 1].account_action_seq;
if (maxActionInd <= pos) {
    break;
}

Error msg

There is no identity with an account set on your Scatter instance.

possible reasons

• something wrong with the api getIdentity
• db error

When there are multiple concurrent getIdentity requests, scatter will only return the first one.

Thats's a matter of scatter

test case:

await (eosplayer.scatter.getIdentity({ accounts: [eosplayer.netConf], }));
await (eosplayer.scatter.getIdentity({ accounts: [eosplayer.netConf], }));
await (eosplayer.scatter.getIdentity({ accounts: [eosplayer.netConf], }));

expect

three results are returned.

result

only one result are returned.

conclusion

thus, when you call several eosplayer.getIdentity() concurrently, only the first request will return, and the others will die in the scheduler

solution

using a message queue

for now, chain.getActionCount returns the max action seq value.
it may cause some understanding problems.

thus, this interface needs to be adjusted.