Metamask: Ether.js works fine on desktop but not with metamask app (android/ios)

Here’s a draft article based on your description:

Metamask: Ether.js Works Fine on Desktop But Not with Metamask Mobile App

As a Dapp developer, I’ve encountered several issues while using the popular Metamask extension to interact with my Ethereum smart contract. In this article, I’ll share my experience with getting Metamask to work correctly on both desktop and mobile devices.

The Issue:

My issue started when I decided to use MetaMask on Android and iOS devices to connect to my Dapp’s mainnet connection via the Ether.js library. Initially, everything worked fine, but as soon as I installed the Metamask app on my Android or iOS device, I encountered an error.

The Error:

The error message typically reads:

TypeError: Cannot read property 'default' of undefined

or a similar variation depending on how MetaMask is configured in your Dapp’s mainnet connection. This issue seems to occur even when the Ether.js library works fine on my desktop machine.

The Solution:

After some trial and error, I discovered that this issue occurs due to the way Metamask handles the default property of the Web3 provider object returned by Ether.js.

To resolve this issue, I’ve found two potential solutions:

• Use a different provider: One solution is to switch from using Ether.js directly with MetaMask to using a different provider like Truffle.js or Hardhat. These libraries provide more control over the Web3 provider and may be less prone to errors related to the default property.

• Set the defaultProvider option on Ether.js: Another solution is to set the defaultProvider option on the Ether.js library itself, which can override any errors that occur due to the default property.

To enable these solutions, you’ll need to modify your Dapp’s mainnet connection code using one of the following methods:

Solution 1: Use a different provider (Truffle.js or Hardhat)

const Web3 = require('web3');

const ethers = require('ethers');


const provider = new ethers.providers.Web3Provider();

provider.setBlockchian('mainnet'); // Set mainnet provider


const contract = new ethers.Contract(contractAddress, abi);

Solution 2: Set the defaultProvider option on Ether.js

const Web3 = require('web3');

const ethers = require('ethers');


const provider = new ethers.providers.Web3Provider();

provider.setBlockchian('mainnet', {

  defaultProvider: '

});

Conclusion:

While the Metamask app can still connect to my Dapp’s mainnet connection via Ether.js, I’ve found two potential solutions that resolve this issue. These solutions require modifying your Dapp’s code using one of the methods above.

By implementing these solutions, you should be able to get MetaMask to work correctly on both desktop and mobile devices when connecting to your Ethereum smart contracts using Ether.js.

Note: These are just temporary workarounds and may not be the most efficient solution. I recommend exploring other options for resolving this issue or consulting with a professional developer if needed.