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?
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.
Hrm, I got it via F-Droid myself today. So it apparently got pushed out somehow. Good to know it isn’t on the Play Store though.
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.