You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MetaMask no longer works if Frame Companion is enabled. The browser extension lacks a "flip" feature (like in Rabby Wallet) where the user is given an option whether to use one or another, else some users may not understand why is MetaMask no longer working. Perhaps it exists and I'm not aware of it?
Besides, having MetaMask, Rabby Wallet, and Frame Companion concurrently enabled creates some sort of extension conflict, like in my particular case, a TypeScript runtime error is thrown and caught by a Next.js application in development when switching browser tabs, as shown in the below screenshot:
Disabling the "conflicting" wallet browser extensions resolves the issue. Very annoying for Next.js developers. (no clue whether other frameworks are affected though)
The text was updated successfully, but these errors were encountered:
MetaMask no longer works if Frame Companion is enabled. The browser extension lacks a "flip" feature (like in Rabby Wallet) where the user is given an option whether to use one or another, else some users may not understand why is MetaMask no longer working. Perhaps it exists and I'm not aware of it?
Besides, having MetaMask, Rabby Wallet, and Frame Companion concurrently enabled creates some sort of extension conflict, like in my particular case, a TypeScript runtime error is thrown and caught by a Next.js application in development when switching browser tabs, as shown in the below screenshot:
Disabling the "conflicting" wallet browser extensions resolves the issue. Very annoying for Next.js developers. (no clue whether other frameworks are affected though)
The text was updated successfully, but these errors were encountered: