Hey everyone. If I’m spamming my repo too much let me know.
Since v37 came out, development is going at whirlwind pace, and there are still frequent complaints about crashing/no logins for 0.17.x, I decided to post again, but this time bearing good news.
I finally made a Jerboa version where you can log into both 0.17.x and 0.18 accounts.
Unlike the main repo my release is also compatible with phones running Android 5.0.
Check it out and let me know if this is helpful for you. I’m trying to get this merged in as PR#908 but Woodpecker is giving me a hard time.
I’m not seeing any issues using the app with a 0.17.x other than the pop-up at the start, are things not working correctly for me? Breaking backwards compatibility isn’t great, but at least we are moving forward it’s progress. As a developer myself I’m happy with a few teething issues and to be honest I’m surprised there aren’t more than I have seen, it really speaks volumes to those that have committed to the project!
You simply can’t login to a 0.17.x server.
Is it possible for your changes to be merged into the original jerboa?
I’m not sure if the post text was changed, but he says, that he tries to get a pull request (for a merge), but seems original Jerboa maintainer isn’t jumping on it. But I don’t know any details
I have a PR open, I’m wrestling with the automated build system (woodpecker) that complains when I forget to put a space after // and things. I fixed all of it then it somehow got stuck compiling.
Be patient, I think the main developers will have another look through it in the next couple days.
Run ./gradlew lintKotlin to check for lint errors or ./gradlew formatKotlin before commit to automagically fix them. Saved me a ton of time.
Bless you sir/ma’am/honourable one… I’ve been running a normal gradlew and testing my commits on emulators and actual devices, but I’m too used to my if(a)b; else if©d; coding style that I mess up something every time when I try to conform to spacing rules.
Nice, it’s insane the app broke compatibility but I understand they are crunched for time! Adding this back in is important to ease adoption for Lemmy as a whole.
Thanks! It baffles me that the most popular Lemmy app doesn’t work on .world, one of the top two Lemmy instance.
Still supports Android 5.0 and up as always.
Now here’s some good news for people with older phones ☺️. Thank you kind stranger 👍.
Supporting older devices was the original goal of my fork.
Then Lemmy 0.18 and Jerboa v35 dropped breaking things which made using the app annoying or straight up unsuable for some servers.
So I put some work in to at least fix what were the most glaring issues. It’s not a perfect/futureproof solution, the main developers would prefer an interface to pass Lemmy API version with the login and handle things on a version by version basis rather than an issue by issue basis. I can understand their reasoning.
Still, it’s a nice thing to do. I know a few people that have really old smartphones and don’t use any software for social media because of this (they just use way too much resources and the apps usually just hang), now I can suggest Lemmy as a plaform they can most definitely use, even on older hardware, with your forked Jerboa app of course. One of them is really knowledgeable about certain electronics subjects, just kinda out of luck in life (money wise), so he’s stuck using his old phone at the moment, so I will most defintely suggest trying Lemmy with Jerboa now.
I appreciate the effort, as lemm.ee has not yet upgraded. And while I can log in, it won’t keep me logged in. I can see that it initially loads my profile, but then any action (upvote, read a post) returns to anonymous status, and the profile goes missing again. Am I doing something wrong?
I’ve tried logging out, uninstalling, re-installing, logging in again. The problem happens again.
Thanks for this
Thank you very much!!
Thank you! I could finally login back to my lemmy.world account and realised that lemmy.ml was slow af.
