Boost For Lemmy

7051 readers

3 users here now

Community of the Android app Boost for Lemmy

founded 1 year ago

MODERATORS

rmayayo@lemmy.world

New lemmy version breaks the app (lemmy.dbzer0.com)

submitted 11 months ago* (last edited 11 months ago) by TheCreeperFace@lemmy.dbzer0.com to c/boostforlemmy@lemmy.world

13 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Darkassassin07@lemmy.ca 11 points 11 months ago (3 children)

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.

[–] Gestrid@lemmy.ca 3 points 11 months ago (1 children)

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.)

[–] Darkassassin07@lemmy.ca 1 points 11 months ago

Yeah, I've just been to lazy to bother. I'll use boost till google play catchs up. I'm already here after all.

[–] otter@lemmy.ca 2 points 11 months ago

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

[–] walden@sub.wetshaving.social 2 points 11 months ago

I've read elsewhere that clearing the app's cache might help.