Honestly this seems to be an issue with Jerboa caused by the developer. I’m using the Mlem beta on iOS and the dev added support for the 0.18.0 API, but didn’t remove support for the 0.17.x API version. It seems like a user unfriendly choice to break support in this way when so many instances haven’t updated yet. Fair enough to not support them both indefinitely, but it’s going to be really frustrating for both users and server admins if this happens every major update going forward.

Jerboa being open source is cool but it’s proven to be a shitty app pretty quickly. Hopefully it’ll get better with time.

Liftoff and Wefwef are both way better mobile solutions currently

It does, the developers did a really annoying move and updated the app with no backwards compatibility whatsoever

You can downgrade the app, however if it tries to load the default lemmy.ml homepage, it will just crash

You can install this version of the app though which works with older servers but doesn’t crash: https://github.com/ShinyLuxray/jerboa/releases/tag/0.0.34-plus.hotfix1 (I found that in the matrix channel)

I got that message too but I’m still able to post and comment. I was able to dismiss it and it seems like everything works fine. Or maybe I’m just confused with what should be happening?

My version is 0.0.35 from Fdroid so I don’t know if that’s any different? There’s a 0.0.36 from Izzy but it’s a different cert so I’m not sure the difference.

You will need to use 0.0.34 version for Jerboa if you are on the instance that doesn’t yet updated to 0.18.

Most big instances are skipping 0.18 and will wait for 0.18.1 to get new captcha added.

Edit: https://github.com/ShinyLuxray/jerboa/releases/tag/0.0.34-plus.hotfix1 might be a better option as it allows to bypass the issue with default instance being lemmy.ml which uses 0.18 and causing the issue.