Transiction send error "invalid sender" when sending over private Ethereum network

[pavelkrolevets]

Describe the bug

Mobile Metamask fail to send ASK over https:// endpoint of another proof-of-authority network. Error - invalid sender. This indicates that the signature is wrong. It seems the signing function cant generate right sing when chainID !== networkID for private networks. I also tested when chainID == networkID on my local network on

Network Name: ASK Mainnet
New RPC URL: https://blockchain-api-mainnet.permission.io/rpc
ChainID: 222
Symbol: ASK
Block Explorer URL: https://explorer.permission.io/

I am able to receive ASK in the iOS and Android mobile apps. But when I try to send from iOS or Android to another Metamask wallet I receive the error: "Transaction Error - Object [Object]" with no additional information about why it failed.

Screenshots

To Reproduce

1. Add network ASK mainnet in the Mobile Metamask with parameters
   Network Name: ASK Mainnet
   New RPC URL: https://blockchain-api-mainnet.permission.io/rpc
   ChainID: 222
   Symbol: ASK
   Block Explorer URL: https://explorer.permission.io/
2. Send native tokens to another account.

Another way:

1. Run local private network with chainID !== networkID
2. Send tokens to another account

Expected behavior
Transaction should be accepted to the network, but get error - invalid sender. Which indicates that the signature is wrong despite that chainID is provided (222), but networkID is different (2221).

Smartphone (please complete the following information):

• Device: iPhone 6 Plus
• OS: iOS 13.6
• App Version v1.0.1(522)

---

to be added after bug submission by internal support / PM
Severity

• How critical is the impact of this bug on a user?
• Add stats if available on % of customers impacted
• Is this visible to all users?
• Is this tech debt?

[pavelkrolevets]

This maybe related #1820

[evanliuchina]

Got exactly the same problem. Did you find any way to work around @pavelkrolevets ?

[iquidus]

bump.

This impacts all networks in which networkId and chainId do not match. Not just private nets, but live public nets also (e.g ethereum classic & ubiq). Signing transactions with networkId is invalid behavior (not to spec), producing invalid transactions (unless the Ids happen to match).

Users can receive funds to metamask mobile on these networks but only to have it stranded as they can't produce valid transactions. Requiring them to import recovery phrase into an alternative wallet to recover said funds.

[iquidus]

First time looking at the mobile code but here is one such occurrence (and possibly the main culprit?): https://github.com/MetaMask/metamask-mobile/blob/develop/app/components/UI/PaymentRequest/index.js#L292

[jyap808]

Please back port the fix from the main Metamask browser extension.
Network ID <> Chain ID

Thanks

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity. If you feel this was closed in error please reopen and provide evidence on the current production app. Thank you for your contributions.