Web3Auth not initialized

Code

AUTH/WEB3_AUTH_NOT_INITIALIZED

What it means

Web3Auth helpers (challenge/response generation, signatures, etc.) require an active private key/session, but the auth module has not been initialized.

When it happens

Web3Auth is used before an active account is set.

Typical scenarios:

A page calls generateWeb3Auth() before setActiveAccount()
Session was cleared but UI still assumes authenticated state

How to handle

Treat as a client state bug: re-run account initialization or force logout → login.
Include meta.via to identify the call site.