New lemmy version breaks the app
New lemmy version breaks the app
my instance updated to the version 0.19 and it brock the app it shows you as loged in but you can't post (shows a 401 error) filters and block lists are empty and every post is saved when you open the app edit: login out and back in fixed thanks
That may be a separate issue. Have you logged out and back in? They did reset 2fa entirely for everyone, so your previous logins should be invalid.
I'm only using Boost because the update broke Jerboa. Can't login at all using it.
Boost has worked perfectly though, with the exception of not letting me delete posts.
You need to update Jerboa either by using the GitHub release or the F-Droid release. Unfortunately, Google Play hasn't released the update Jerboa that supports the changes Lemmy made yet. (My understanding is that this is a problem on Google's end and that it's not the dev's fault.)
Yeah, I've just been to lazy to bother. I'll use boost till google play catchs up. I'm already here after all.
I've read elsewhere that clearing the app's cache might help.
I barely noticed the update on mobile. A quick log out and log in fixed it for me
The upgrade overhauled some 2FA stuff, and so I assume it logged everyone out to make sure things are secure.
On mobile, that means you need to manually log out and log in. On desktop, the official UI indicates what happened and instructs you to login again
The update broke logins for a lot of instances. Try logging out and back in. It worked for me on multiple accounts
Good call, I was getting "All" in my subscribed tab and logging out and in seems to have fixed it.
visibly sweats
Really hoping lemmy.world doesn't update before this fix
Boost supports Lemmy 0.19 since the last update. But you probably will have to log in again.
Ah dope. Thanks for all the hard work! I wouldn't be able to post all the shit I do without boost <3
We updated just fine, I just had to log out and back in once. Barely noticed it
Clear the app cache.
Boost has been (mostly) fine for me, but you have to log out and back in. My instance updated yesterday.