Closed mikera closed 3 years ago
This is strange @mikera . The session has always been persisted, and I just tried on Firefox and Safari - I closed the browser and opened it again, and I can still access my accounts (session).
Hmm maybe it was Chrome being too aggressive about blocking cookies?
I can reproduce on macOS with Chrome.
There's a setting to clear cookies when you close all windows, but mine is disabled, and Google Chrome still clears the cookies when I close the window. It's a bit puzzling.
Will become less urgent once we have the facility to restore an account with an explicit keypair
If you save your wallet key, you can restore your wallet. It doesn't fix the problem, but at least you don't lose access to your wallet.
We are using session cookies so you need to set Chrome to restore your previous sessions on startup:
Can you see if this works for you @mikera ?
Looking at the ring-session cookie in Chrome I see:
Expires
When the browsing session ends
Shouldn't that be some future time?
We can explicitly set the expiration for the cookie, but we need to set it to a distant future since we don't have sign-in, and once the cookie expires, the user will lose their wallet.
Setting the expiration is explicit, and we don't depend on the browser's session behavior, so it seems a better idea @mikera .
If I close my Chrome tabs (on windows) but then open conex.world again, I appear to lose all my previous accounts and session data.
It it possible to retain these? e.g. with a session cookie?