Daniel Sinclair

@edxeth Currently the peer version is not supported and you should receive a package manager warning. Feel free to ping here when next-auth v5 is out of beta, and we...

Auth.js seems to be approaching a production release of v5 soon, so we will begin working on this. We are also evaluating other improvements to the Authentication/SIWE flow. Do you...

Will think about this! There have some improvements in WalletConnect v2 that makes this more feasible.

@MickaelNeves I believe this caused by the version of `next-auth` that you have adopted. Please use `4.20.1` or earlier. A bug/API change was introduced in later versions, and we will...

Have released [@rainbow-me/[email protected]](https://github.com/rainbow-me/rainbowkit/releases/tag/%40rainbow-me%2Frainbowkit-siwe-next-auth%400.3.0) to support more recent versions of `next-auth`. Let me know if that resolves your issue. Reference the [Migration Guide](https://github.com/rainbow-me/rainbowkit/releases/tag/%40rainbow-me%2Frainbowkit-siwe-next-auth%400.3.0)

I see. The `No matching key. keychain` error is actually a WalletConnect error that (unfortunately) still fires from their libraries. But this sounds like an Argent specific problem. I was...

@malteish Good find. I'm able to reproduce the behavior you're seeing. I believe the issue is related to calling Wagmi's `signMessage` hook in the Safe environment, with RainbowKit awaiting a...

@malteish Yes, you're right. Was able to isolate the issue to `next-auth` session handling. ```const { status } = useSession()``` is not updating to `authenticated` in the Safe environment. Still...

@malteish Will keep this issue open to see if a better solution is presented. I'll also relay to the Safe team to see if there is guidance on how to...

Noticed some merge conflicts too with v2