Issue when no wallet is attached to the browser #110
Conversation
|
This is not the ideal scenario, but for now this seems to fix the problems related to builds. Ready for review @xavikh |
| }, | ||
| connectors: [ | ||
| walletConnect({ | ||
| projectId: PUB_WALLET_CONNECT_PROJECT_ID, | ||
| metadata, | ||
| showQrModal: false, | ||
| }), | ||
| injected({ shimDisconnect: true }), | ||
| // coinbaseWallet({ appName: metadata.name, appLogoUrl: metadata.icons[0] }), |
There was a problem hiding this comment.
Right now coinbaseWallet only works without SSR. If we enable it, it fulls the console with errors.
We can enable it if we go to prod, but at least when developing it's quite annoying
There was a problem hiding this comment.
If we don't find a fix then we should consider rolling back enabling SSR
There was a problem hiding this comment.
The warning/error appears in general in Next, doesn't matter if SSR in wagmi or not.
To be clear, it does work. It just shows an error in the console because the backend fails to run that piece of the code.
| }, | ||
| connectors: [ | ||
| walletConnect({ | ||
| projectId: PUB_WALLET_CONNECT_PROJECT_ID, | ||
| metadata, | ||
| showQrModal: false, | ||
| }), | ||
| injected({ shimDisconnect: true }), |
There was a problem hiding this comment.
Why don't we want to use the injected one?
There was a problem hiding this comment.
Nope, it comes by default with the Metamask id. If you add it, it shows metamask twice
No description provided.