Metamask doesn't work with ganache with typed message

[shahafn]

NetworkId is compared to chainId in typed-message-manager.

See

metamask-extension/app/scripts/lib/typed-message-manager.js

Line 164 in d68f156

chainId && assert.equal(chainId, activeChainId, `Provided chainId (${chainId}) must match the active chainId (${activeChainId})`)

and

metamask-extension/app/scripts/controllers/network/network.js

Line 123 in d68f156

this.setNetworkState(network, type)

network is set to be the result of the rpc method "net_version" i.e. networkId, and it is compared to chainId, which on ganache-cli aren't the same.

Edit: The bottom line is that if chainId is provided in the message, Metamask will always throw on Ganache.

[shahafn]

Is there any update on it @kumavis ?
It's currently impossible to work with Ganache with MM and typed message, without intentionally inserting a bug that would pass network id as chain id.

[forshtat]

@kumavis is anyone here?

[drortirosh]

Note that this bug means that getTypedData() method can't be used on network where chainid!=networkid - most notably is local testing on geth/ganache - but also Ethereum Classic

[rekmarks]

I regret that we haven't been able to address this issue. We are looking into this, and will hopefully be able to ship a fix soon. Until we fix this, you should be able to omit the chainId from your signing parameters for local development work / testing.

[drortirosh]

Any ETA for the fix?

Its very problematic to create different contracts for local and remote testing

[rekmarks]

@drortirosh #9552 should land tomorrow, and hopefully be included in a feature release this week.

[drortirosh]

Is this fix already released? the latest published chrome extension is 8.0.10, dated 22-Sep-2020

[rekmarks]

It'll be fixed in version >=8.1, which has already shipped on Firefox, and will probably ship on Chrome early next week.