Meh, if it is then it is (e.g. I could use another app, or like… actually make a password that I can remember hehe:-), but either way I’d at least like to know.
This is the second time now that a week after I log into the app a pop-up has come up titled “Login Session Expired”, continuing with “Your login session is no longer valid. Please login again.” The options are to login or logout, I can’t simply click away. Force-closing the app does work to get around this requirement - except obviously I lose my place in whatever I was reading through, but I can vote and comment again. So obviously the “expiration” was false if I can continue beyond it, but I forget for how long that works before the expiration dialogue comes back again.
Is this normal behavior? If not then are there any ideas why I am seeing it - like perhaps my installation via FDroid rather than the Play Store could be a factor? If it is, then how do people usually deal with this - the force close and reopen method I’ve been using so far?
You must log in or register to comment.
That is strange! I logged in once and have never had to re-login on Voyager
That is very good to know, thanks!
Although you are using PieFed rather than Lemmy, so perhaps there’s a difference in how it accesses the back-end. (Even so it offers hope that if I were to switch to a PieFed instance…:-)
Not for me. Can’t remember the last time I had to login
At least you’re getting it after login. I’ve gotten it several times while in the middle of a lengthy comment. I think it’s related to instance because sometimes I just can’t login and I have to re-register my server.
I’ve responded to several comments since then, and voted, and read several posts - basically it’s back to normal. Until the pop-up reappears.:-(
I don’t even know why a session needs to “expire” in the first place, but it is what it is. Voyager is a very nice app and I hope I can find a way to use it.
Are you on the latest version of the app?
I just updated to version 2.48.0 yesterday after such a pop-up occurred and it has not happened yet, though I would think there hasn’t been enough time for it to trigger yet. Before that I don’t recall FDroid nagging me about it so I thought it was up to date but can’t recall perfectly (I do have it set up to check every 2 days).
Oh I did forget to mention that this style of pop-up has occurred on two separate devices, both Android, and both using this account. The other device is somehow running only 2.47.4 despite FDroid saying that it is up to date.
If you think that accessing Lemmy from two separate devices, running different versions of Voyager, could be causing the problem, then I would be happy to abandon one of them in order to salvage the other?
Might want to ask your instance Admins about that.
I have never had it ask me to relogin to Lemmy.world or any of the other defunked instance I had accounts on.
I also have it installed from fdroid.Fwiw, this behavior does not occur in either the Summit 3rd-party app or the standard web UI with Firefox on Android - both with this same account on discuss.online. So it does seem unique to Voyager, or at least something between Voyager and this instance. But that’s great to know that it’s high unusual and others installing from FDroid aren’t seeing this.
That might be something from your instance, I have three accounts on three different instances and I never had to log back in on any of them, not even the account that I barely use.
that’s most of why I use voyager, lemmy.ml makes me log in with 2fa every couple days
This started happening to one of my accounts a while ago too, except mine expires much more frequently, several times within maybe a few hours, made that account unusable with the Voyager app. It doesnt happen with the Blorp app tho.
Just today another account of mine that Id been using gave me the session expired popup as well. So far this lemmy cafe account hasnt timed out, but both my other ones have now.
This never happens to me using Summit - so yeah it seems app-dependent, or at least presents that way to my naive eyes. Thanks for the suggestion about Blorp:-). And that’s good to know that Voyager is causing that for you regardless of account (& presumably instance).
Maybe we are just using the app wrong, somehow, or something, I dunno. 😜
