I immediately updated to v0.0.35 as soon as i saw it on GitHub, to realize i get kicked out of the app for having an account on a Lemmy instance still running 0.17. Reinstalled v0.0.34, except that now crashes on startup, probably since the default instance it uses is on 0.18.
Do I have to use 0.0.35 in anonymous mode until my instance updates to lemmy 0.18, or is there some workaround?
The 0.18.0 lemmy release is going official tomorrow, I’d assume lemmy instances will be quick enough to pick it up once available.
Even so, breaking Jerboa app access to every lemmy instance that isn’t lemmy.ml is a bit of a big oops. Especially during a period of tons of new users who may not understand what the problem is. Hopefully steps can be taken in the future so that it doesn’t happen again.
To be fair that version of Jerboa is not currently on the app store. There’s definitely gonna be some hoops to jump through with the timing though.
Yup, Google Play releases are pretty slow. It’s alpha software, so issues are to be expected.
There is talk about supporting both the previous and current lemmy versions each release, but that takes a lot of work and nobody has done it yet. There is interest, so maybe the lemmy 0.18 -> 0.19 upgrade will be smoother.
It’s going to be a bit rough over the next week or so.
If I understood correctly Lemmy 0.18.0 contains breaking changes which need an adoption for current clients to work. Since I’m pretty sure that most instances will upgrade asap that step was necessary.
Both Lemmy and Jerboa are v0 releases and as such should probably be considered unstable (assuming semantic versioning). The average user probably won’t know or care - and why should they? So it’s not great in that sense.
I had the same message when I opened .35 but the app continued to work like normal. My server is on .17
Just note, there are two things I know of that cause crashes with a 0.17 server:
- mark as read
- login
As long as you don’t do either of those (i.e. you’re already logged in on a previous version), things should largely work.
For me, saving a post also crashes the app. But when I open the app again the post is saved. So at least the saving itself works.
Yeah, it’s a problem largely with understanding the response. A lot of little things changed, and Jerboa doesn’t use all of them, so the breakage can seemingly be random.
I got the error and it would not stay on my “subscribed” feed so i logged out and back in - or tried to anyway - only to discover i cant login. Writing this from the web ui and somewhat annoyed. Downgrading until my instance updates i guess.
It seems like there are a lot of bugs going around but Jerboa works well
Downgrade to jerboa 0.0.34, long press, tap app info (circle with an “i” inside, tap storage, tap clear storage, then reboot as i think some stuff from 0.0.35 is still in RAM and causing 0.0.34 to crash. I was having the crash too until i rebooted the phone
I’ve also noticed that the inbox retains read messages even after they are cleared. They keep coming back.
If you downgrade you need to completely uninstall the app, deleting settings and caches etc., then install again.
