@walter.rodriguez
Correct. Our backend is using update user endpoint for creating the session token. However following that session issue I assume there are two expirations possible. One is from the client (expiration of the session) and second is expiration of the session token.
Do you have maybe information how long the session can be ongoing with expired session token (see the other issue)? I assume that’s an issue for us, that the user continues using SDK, when the session token expired. However that’s hard to debug, because of having this implicit timeout that we cannot control.
