IDK why but the app isn’t logging me in today. I also seem to be having issues logging into some instances through the website, but I’m not getting any errors or anything. It just goes like it’s working but then when the page reloads, I’m not logged in. Took me like 15 tries just to get to the create post button.
The weird thing is I can still access my profile, I just can’t view my subscriptions or make posts because I’m not logged in. Usually if I’m not logged in, I can’t see my profile either. 🤨
Don’t know if the issue is the app or the service itself.
I was having that issue earlier myself. Removed my account from the app then just added it back. Seems to be fine now ¯\_(ツ)_/¯ best of luck!
If you’re having issues with one of your accounts in Liftoff! you might need to remove your account and log back in. On the add account page you can long press an existing account to remove it and log back in. But if your instance’s website isn’t logging you in reliably either, there may be something else going on or you might need to clear cookies for your Lemmy instance’s website as well.
There was a security vulnerability exploited on multiple instances last night and a lot of instance admins invalidated all existing login tokens. I don’t know if there’s a Lemmy API response for invalid sessions, but if so, it appears we’re not handling it in Liftoff. Regardless, I expect there to be changes to the Lemmy API relatively soon to address some shortcomings in the way login sessions are handled. When that happens, we’ll try to handle invalidated sessions in a nicer way (i.e. with a banner saying you’ve been logged out potentially).
invalidated login tokens
Ah, ok yeah. That’s probably it. Yiffit even has a sticky saying they did this but it read like they just force logged everyone out. Now I understand what they really meant.
That worked! 😄
I had that problem this morning. I uninstalled the app and reinstalled it. That worked for me.
Are you posting from a different account or something?
I had a similar issue, but mine was caused by having a vlemmy account logged in on the app alongside others. Looks like if an instance closes it can freeze loading content from all other instances. This is probably a bit of a bug.
