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
The React authenticate function returns a void promise authenticate: (options?: AuthenticateOptions) => Promise<void>;
Feature / Enhancement Description
It would be nice to have a response to handle. Either for errors or anything else. In the the docs at https://docs.moralis.io/moralis-server/users/crypto-login#metamask it appears that there should be some response in the JS SDK although looking through the types it seems void as well (moralis/types/index.d.ts).
Example Use Case
Any time you want to authenticate a user. Maybe catch errors.
Alternatives / Workarounds
I think its probably fine for most use cases to just use the authError from the context. It just will not allow catching the error. In terms of development philosophy I dont actually know if it matters or not that the error fall through to console. Its probably better I'm not sure about that.
The text was updated successfully, but these errors were encountered:
New Feature Request
Checklist
Current Limitation
The React authenticate function returns a void promise
authenticate: (options?: AuthenticateOptions) => Promise<void>;
Feature / Enhancement Description
It would be nice to have a response to handle. Either for errors or anything else. In the the docs at https://docs.moralis.io/moralis-server/users/crypto-login#metamask it appears that there should be some response in the JS SDK although looking through the types it seems void as well (moralis/types/index.d.ts).
Example Use Case
Any time you want to authenticate a user. Maybe catch errors.
Alternatives / Workarounds
I think its probably fine for most use cases to just use the authError from the context. It just will not allow catching the error. In terms of development philosophy I dont actually know if it matters or not that the error fall through to console. Its probably better I'm not sure about that.
The text was updated successfully, but these errors were encountered: