Not connected (Firefox + MetaMask)

[fryorcraken]

Using the following code snippet:

 import {ethers} from "https://unpkg.com/ethers@5.7.2/dist/ethers.esm.min.js"

const provider = new ethers.providers.Web3Provider(window.ethereum, "any");

connectWalletButton.onclick = async () => {
        try {
            accounts = await provider.send("eth_requestAccounts", []);
        } catch (e) {
            console.log("No web3 provider available", e);
        }
    };

I am getting

Error: Not connected
    n http://127.0.0.1:8080/:1
    setTimeout handler*doSend/< http://127.0.0.1:8080/:1
    doSend http://127.0.0.1:8080/:1
    doSend http://127.0.0.1:8080/:1
    request http://127.0.0.1:8080/:1
    buildEip1193Fetcher https://unpkg.com/ethers@5.7.2/dist/ethers.esm.min.js:1
    send https://unpkg.com/ethers@5.7.2/dist/ethers.esm.min.js:1
    onclick http://127.0.0.1:8080/:281
    EventHandlerNonNull* http://127.0.0.1:8080/:279

On Firefox 106.0.4 (64-bit) (Linux Fedora) + MetaMask 10.22.1
ethers@5.7.2 (as you can see from the snippet).

The code works fine with Chrome + MetaMask and with Brave.

Here is the full app https://github.com/waku-org/js-waku-examples/blob/master/rln-js/index.html (only upgraded locally to latest ethers)

Here the app deployed: https://examples.waku.org/rln-js/ (same code except that it uses ethers@5.0.7

[ricmoo]

Are you checking that window.ethereum is defined? In JavaScript, passing in an undefined value, is the same as passing in “nothing”.

Can you console.log(window.ethereum) to make sure it is a valid EIP-1193 provider?

[ricmoo]

Is your MM maybe connected to a local host network in debug mode or such? Based on the object, those errors look like they are internal.

Make sure you have selected the correct network in MM? OtherwiseC you might have to ask them what is going on. :s

[fryorcraken]

I can see connect: false. Is this still the best way to connect:

 accounts = await provider.send("eth_requestAccounts", []);

?

[fryorcraken]

I guess this is not an ethers issue because with

        try {
            accounts = await window.ethereum.request({ method: 'eth_requestAccounts' });
        } catch (e) {
            console.log("No web3 provider available", e);
        }

I still get

 No web3 provider available Error: Not connected
    n http://127.0.0.1:8080/:1
    setTimeout handler*doSend/< http://127.0.0.1:8080/:1
    doSend http://127.0.0.1:8080/:1
    doSend http://127.0.0.1:8080/:1
    request http://127.0.0.1:8080/:1
    onclick http://127.0.0.1:8080/:285
    EventHandlerNonNull* http://127.0.0.1:8080/:283
    ```

[ricmoo]

To my knowledge, yes. That is an internal variable to MetaMask though, so I’m not certain to what extent it actually means connected; could just mean it heard back from a server, for all I know. :)

[fryorcraken]

I am also using Goerli Testnet (as defined by default in MetaMask) which could be an other source of issue.

I am taking the discussion over to MetaMask https://github.com/MetaMask/metamask-extension/discussions/16579