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
I believe it's not a bug, and just the documentation is not covering all the getMessageParams possible arguments. Checking the source code, I can see that you can pass iat, which will work fine. E.g.:
const getMessageParams = async () => ({
domain: window.location.host,
uri: window.location.origin,
chains: [1],
statement: 'Please sign with your account',
iat: new Date().toISOString(),
});
It is a bug. This field is required as per ERC-4361, so if it was a docs issue then not providing it should be a compile-time error. Second, even if it was optional, the field shouldn't be included at all instead of being an "undefined" string
Link to minimal reproducible example
https://lab.web3modal.com/library/wagmi-all/
Summary
Login with email
List of related npm package versions
latest
The text was updated successfully, but these errors were encountered: