• A new version (v0.18.0) of the Lemmy server was released a couple of days ago, and it changes the API used by apps significantly.
• Your account is on the lemmy.world instance, which hasn't upgraded yet because the new version is missing an important bot-acount-signup defense feature that is gonna get re-added in a Lemmy patch-release soon. So it's still running v0.17.
• A new version of Jerboa was released (v0.35) with compatibility for the new version of Lemmy.

If Jerboa is working ok for you, you can ignore the error. It will fix itself "real soon now" when lemmy.world upgrades. If Jerboa is broken you can uninstall it and reinstall v0.34 from https://f-droid.org/en/, https://github.com/ImranR98/Obtainium, or direct from Jerboa's GitHub. All of these are a little more complicated than installing from the play store, but not too bad. If you downgrade, be prepared for the opposite message to come soon and you'll want to upgrade again.

If Jerboa is working ok, I suggest you wait it out.

It's telling you the instance that you are on hasn't updated their server to the new Lemmy version yet. The admin of lemmy.world mentioned he would update as soon as 18.1 drops, as it includes a vital captcha feature for anti-bot measures. Essentially, you can disregard this, just know things may be wonky for a little bit.

A new version of the Lemmy server software was released recently, version 0.18. It appears that the Jerboa app is now expecting servers to be on that new version. It looks like you're connecting to the lemmy.world server, which has not upgraded yet. They are waiting for a feature that won't be ready until 0.18.1

Unfortunately, there's not a lot you can do to fix this yourself - it's up to the people administrating lemmy.world to upgrade their server when they're ready.

IMO, Jerboa should not have locked out old versions so quickly.

I think it's because the new version of Lemmy was released. Jerboa updated, expecting this new minimum version, but lemmy.world has yet to upgrade to the latest release.

It works just fine on the website as a temporary workaround.

Yeaaaah, im new to Lemmy just today, but already encountering this is rough xD. I'll just use it on desktop meanwhile.