Open yunlonglee opened 3 years ago
@yunlonglee Can you still reproduce this bug? If so, can you provide some more details?
We get these occasionally via Sentry. We use bnc-onboard
and reconnect automatically unless the wallet is locked, like so:
const isMetaMaskAndLocked =
previouslySelectedWallet === 'MetaMask' &&
typeof (window as any).ethereum?._metamask?.isUnlocked === 'function' &&
!(await (window as any).ethereum._metamask.isUnlocked());
Among 59 error events, 75% had browser logged as "Chrome Mobile iOS 76.0.3809" (OS: iOS 13.1), 25% as "Chrome Mobile 77.0.3865" (OS: Android 10). Is there a way to log MetaMask version to track this down a bit more precisely?
I'm also getting this error via Sentry.
What checks should we be running to prevent this bug from being reported in Sentry?
Hello, I have also encountered this problem. Have you solved it?
I have the same problem, is there any solution?
I have the same issue using MM in app browser on an approval trx?
Did someone got a solution?
I'm getting the same error, always on mobile :
Same on sentry. @freeatnet your solution works across all devices?
Not sure why. Showing this error. Metamask received invalid isUnlocked parameter