How to recover typed signature produced by MPC core kit

Working with with the MPC core kit react redirect example, I am struggling with verifying the signature produced by the sample using the metamask eth-sig-util package.

Using the metamask live demo, I can sign a legacy transaction using metamask, then use the recoverTypedSignatureLegacy function to recover the signature. The typed message used in that example mirrors the message structure in the web3auth example.

If I sign the exact same message in the web3auth sample, I receive an error validating the message: Error: Invalid signature v value

Can someone point me to an example of how to validate the signature produced by the example?

Please refer to this gist for more details: Details related to attempting to validate web3auth signed message · GitHub

@d-smith Thanks for your recent communication.

Your issue has been forwarded to our team and we will get back with further updates once more information becomes available.

I’m facing a similar issue, where the signTypedData method is producing an invalid signature (64.5 bytes length). This is a pretty serious issue, as it’s not working properly.