After the latest Chromium update, our signTypedData function broke. Users started seeing the error shown in the screenshot, and the extension console looks like what’s shown in the screenshot. The issue gets resolved when users toggle OFF Settings > Experimental > Improved Signature Requests.
It started to occur after the latest update.
Additional info: We discovered that changing the name of our primary type from ‘Permit’ to anything else stops MetaMask from throwing this error. Even though Improved Signature Requests toggled ON
same issue here. please fix!!!
در ۲۳ سپتامبر ۲۰۲۴ ۱۲:۵۳:۰۰ (GMT+03:30)، elvaleryn via MetaMask notifications@metamask.discoursemail.com نوشت:
Hi @elvaleryn
I recommend reaching out to the MetaMask support team for this issue so they can look into it.
In order to do this please visit https://support.metamask.io/ and click on the large blue “Start a Conversation” bubble located in the middle right of the page. A live chat bot will appear on your screen. It will give you an automated response at first, but afterwards you should be able to contact the support team directly.
Check my reply here above please and contact the MetaMask support team by following the link and steps I shared.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
