CoinbaseAdapter "Signature do not match address of the message."

[silver]

Hi,

I have basic boilerplate usage of CoinbaseAdapter:

import { CoinbaseAdapter } from "@web3auth/coinbase-adapter";

// ...

const chainConfig = {
    chainNamespace: CHAIN_NAMESPACES.EIP155,
    chainId: "0x2105",
    displayName: "Base Mainnet",
    rpcTarget: "https://mainnet.base.org",
    blockExplorerUrl: "https://base.blockscout.com",
    ticker: "ETH",
    tickerName: "Ethereum",
    logo: "https://github.com/base-org/brand-kit/raw/main/logo/in-product/Base_Network_Logo.svg",
};

const privateKeyProvider = new EthereumPrivateKeyProvider({
    config: { chainConfig },
});

const web3AuthOptions = {
    this.clientId,
    web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_DEVNET,
    privateKeyProvider,
};

const web3auth = new Web3AuthNoModal(web3AuthOptions);

const coinbaseAdapter = new CoinbaseAdapter({
  clientId: this.coinbaseProjectId,
  sessionTime: 86400,
  web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_DEVNET,
});
web3auth.configureAdapter(coinbaseAdapter);
        
await web3auth.init();
await web3auth.connectTo(WALLET_ADAPTERS.COINBASE);
await web3auth.authenticateUser(); // error here!

What happens is that it opens the popup for Coinbase (btw I need to turn off my Adblocker to see this popup ). I can press Sign, Coinbase does signing, popup closes and then error in log:

Failed to authenticate user, ,message verification failed {type: 'Signature do not match address of the message.'}

Error: Failed to authenticate user, ,message verification failed
    at verifySignedChallenge (baseControllers.esm.js:806:11)
    at async CoinbaseAdapter.authenticateUser (baseEvmAdapter.esm.js:42:13)

[Ayush]

Hey @silver thanks for the details, I’ll try to reproduce the issue and update you.

[silver]

Thanks, let me know if you need additional info.

[silver]

Hei @Ayush did you have any luck - was my code sufficient for reproducing the issue? Thanks!

[Ayush]

Hey, I’m able to replicate the issue. I’ll update you as soon as possible

[chai]

we’ve fixed this now. Thanks for reporting

[silver]

Great do I need to wait for new release, or this was fixed internally and should already work with existing version of the SDK?

[yashovardhan]

This error is fixed in the latest version of the SDK, please update your packages.