In an expo managed workflow project etherjs fails with Parse error from the server

The below code throws an exceptions

useEffect(() => {
    async function doSomething() {
      try {
        const provider = new AlchemyProvider(
          'kovan',
          "*********************"
        );
        const network = await provider.ready;
        console.log({ network });
        console.log({ connection: provider.connection });
        const blockNumber = await provider.getBlockNumber();
        console.log({ blockNumber });
      } catch (e) {
        console.log("Failed:", e.message);
      }
    }
    doSomething();
  }, []);

Exception

Failed: bad response (status=400, headers={"date":"Sun, 28 Feb 2021 00:27:35 GMT","vary":"Origin","content-type":"application/json","content-length":"83","server":"Apache"}, body="{\"jsonrpc\": \"2.0\", \"id\": null, \"error\": {\"code\": -32700, \"message\": \"Parse error\"}}", requestBody="{\"method\":\"eth_blockNumber\",\"params\":[],\"id\":42,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="https://eth-kovan.alchemyapi.io/v2/***********", code=SERVER_ERROR, version=web/5.0.13)

other logs:

Object {
  "network": Object {
    "_defaultProvider": [Function func],
    "chainId": 42,
    "ensAddress": null,
    "name": "kovan",
  },
}
Object {
  "connection": Object {
    "allowGzip": true,
    "throttleCallback": [Function throttleCallback],
    "url": "https://eth-kovan.alchemyapi.io/v2/****************",
  },
}

If rather than configuring the AlchemyProvider I use getDefaultProvider(‘network’) it works but of course the connections are throttled.

I have another project with the same code that works but it’s configured with “bare workflow”. Both projects have the Etherjs shim (but I don’t think it matters)

I could reproduce the problem with Curl:

curl --location --request POST 'https://eth-kovan.alchemyapi.io/v2/lbJ3HMDaSHXyDaZ6r_1h1HUQpA84OQVp' \
--header 'Content-Type: text/plain' \
--data-raw '{\"method\":\"eth_blockNumber\",\"params\":[],\"id\":42,\"jsonrpc\":\"2.0\"}'

In this case, I got the Parse error

Rather than if I do:

curl --location --request POST 'https://eth-kovan.alchemyapi.io/v2/lbJ3HMDaSHXyDaZ6r_1h1HUQpA84OQVp' \
--header 'Content-Type: application/json' \
--data-raw '{"method":"eth_blockNumber","params":[],"id":42,"jsonrpc":"2.0"}'

I got the correct response.

So it seems Etherjs is serializing in two different ways in my two expo projects.

[ricmoo]

Cool. I can look more into that tomorrow. I don’t use Expo, so I don’t know what bare and whatnot mean, but I can experiment.

You must specify all the API keys. You are missing etherscan and pocket. If you add those, you should stop getting that warning in your console. The performance and security of your app will also be improved. 😃

[sambacha]

your metro config should include this:

module.exports = {
  resolver: {
    extraNodeModules: require('expo-crypto-polyfills'),
  },
};

see this repo for more details https://github.com/draftbit/expo-walletconnect-demo

idk you can close this @ricmoo