Open nullstyle opened 9 years ago
I don't think WalletNotFound
error is a bug in js-sdk. It can throw WalletNotFound
only if server responds with a JSON containing code
field equal not_found
. But a user entered existing username because she successfully opened login_v2
view in stellar-client. Is wallet server behind a caching layer (CloudFlare)? It's strange so it'd be good to investigate more.
There are samples with other errors too:
InvalidSignature
- this can be happening when user changes password using one machine but is permamently logged in the other machine. In such situation he tries to get a current lock version (wallets.getLockVersion
) but walletV2.getPublicKey
(called from signed-json.js
) throws errors.RecordNotFound
because walletId
has changed.invalid aes key size
- all samples from a single user so far and possibly from a farmer (check referer) who could be playing with frontend code.Everything is behind cloudflare, but it should bypass caching for the api actions, especially if they don't provide any cache headers themselves.
https://app.getsentry.com/gostellarorg/stellar-client/group/42133629/
This may be a wallet-js-sdk error. The underlying error is "WalletNotFound", but that doesn't make sense since there appears to be a valid logged in session (meaning at some point the wallet existed)