
This error goes away after login but appears again after logout

@D5

Please, avoid pinging random people 😅

You get this after running account.get() after logout, right?

If so, that's expected, because it means the user is not logged in (there's not an active or valid session)

Can't it go away

???

What do you mean?

Will this error keep showing?

If you mean removing the error, I think not unless you fork the SDK. But you can just ignore it as it should not affect the app behavior or similar

If you try to run account.get() without a session, then yes, but as mentioned it's something you can just ignore

ok thankyou
Recommended threads
- How to reduce DB Reads?
I just noticed that I hit the 500k db reads limit on my very small next js app with the most data being present in one collection having around 50 documents. ...
- Getting issue while migrating from Self ...
i try to migrating my project but when do this error come and dont allow to crate that migration
- Need help setting up this error is showi...
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy. If you're the app developer, register the redirect URI in the Google Cl...
