CoinbaseAdapter “Signature do not match address of the message”

Hi,

I am using no-modal version 9.1.0 and coinbase-adapter 9.0.2 and I am still receiving the exact same error as before in CoinbaseAdapter “Signature do not match address of the message.” - Help - Plug n Play - Web3Auth Community

Can I get more information on what was done and what version or code should I be exactly using? This is now critical for me.

image

Hi Silver Sepp,

Let’s get your issue sorted. Here’s a summary of the details you’ve provided:

  • SDK Details: Plug n Play
  • SDK Version: no-modal version 9.1.0 and coinbase-adapter 9.0.2
  • Platform: (Information not provided, please specify if relevant)
  • Issue: Error - “Signature do not match address of the message.”

To help you better, could you please share the following additional details if relevant:

  1. Your Web3Auth initialization and login code snippets.
  2. The verifier name and the login method if the issue is related to custom authentication.
  3. If you are using your own authentication, please provide the JWKS endpoint and a sample idToken (JWT).
  4. A browser console screenshot of the error for better diagnosis.

Thank you for including the link and the image—these are already very helpful.

Your prompt response will help us resolve this issue faster.

This response was generated by the Web3Auth Bot, and a person from the Web3Auth team will come and give a more detailed answer to your query as well.

Hey @silver, I’ll check and try to reproduce it on my end. I’ll update you.

Hei, any luck with this?

Hey, I’m still able to reproduce the issue, thanks for informing. We will fix it in the next version.

Could you please let us know when its fixed - I need a fix urgently!

Btw could the issue be that Coinbase is initiating a WebAuthn flow and returning the response in CBOR format and not a simple string signature?

Hei, what is the progress on this. For me this is a blocker and would gladly have it fixed? Is there anything I can do right now?

Hey, we’ll let you know by tomorrow max about the ETA of the fix.

Thank you for the info!

Hey @silver we have fixed the issue, you can test using the same SDK version.

@silver is the issue fixed?

Great, thanks for the update! I’ll let you know soon

Its fixed now seems to be working great!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.