App store version is up.
If you are on Lemmy.world, you need to update your JWT token. Sorry, this was not intuitive and there is no proper error message. This is my fault and we seriously just never got around to this.
Please go to “Manage Accounts” and then tap your Lemmy.world account. Hit “Edit Account”, enter your password, then hit save. You should be back up and running.
This has nothing to do with Memmy, but was a result of them invalidating JWTs because of the incdient that happened last night. Regardless, I will make it more intuitive now and just re-authenticate you.
I understand it wasn’t a Memmy thing - I’m wondering if they’ve invalidated the JWTs every few hours today?
Oh I have no idea. I’ve only just sat down at the computer as I’ve been out all morning. Last I saw last night when I went to bed was that they had invalidated them and that was that. Whatever happened afterward I don’t know about. I wonder why that’s happening?
If I close out of the app and restart, I am forced to re-save credentials. This may be a them thing, but it’s a thing.
Oh jeez, now that’s odd. I wonder if they just are not actually getting saved in the app…that sounds like a more of us issue than them to be fair. Let me look.
Fyi: it’s the same for me. Every time the app is closed, when I reopen it I need to do the “edit account” trick to be officially logged in. In “profile” it shows my username, but in “traverse” it tells me I’m not subscribed to any community, and if I try to comment it tells me I need to log in.
Hopefully this info is useful.
The solution is to delete one’s account from Memmy then re-add it, but for that people need another account saved within the app (otherwise they don’t have the option to delete the first one.)
Just saying in case it can help you narrow down the problem.
You can also re-add your own existing account twice! No need to make a second one.
Awkward fix but a fix nonetheless, mine has been behaving fine all day
I added my account a second time and deleted the first one but it deleted both, lol.
But this seems to have fixed the issue! Thanks @[email protected], @[email protected], and @[email protected]!
I think they did it twice