I’m pretty sure I’ve been running the latest version for a few days, so I don’t think it was an update to the app that broke it, though it does give me some kind of update screen that I can’t read because it immediately crashes.
Just thought I’d post to see what was up, since I don’t see any other posts mentioning it.
Yeah, same here, although my issues startet immediately after the update from Google Play. I use a Samsung tablet with Android.
Ya Jerboa totally disintegrated for me over the past few days, the mobile site sucks too but I switched to wefwef and it basically takes the best parts from both but actually works lol
Jerboa is now broken completely and crashes upon start.
Thunder isn’t loading posts/images without a significant delay.
Liftoff is now the best for me on Android 13/GrapheneOS.
All of these statements could be completely different by next week though.
deleted by creator
Recent versions of Jerboa aren’t compatible with Lemmy v0.17.x, which
lemmy.worldstill runs until some performance issues get ironed out.You can install Jerboa v0.34 from F-droid, Obtainium, or by downloading the APK from Jerboa’s github. Uninstall first if you installed from the play store.
The incoming masses aren’t going to understand any of that. They’re going to install it off the Play Store, have it crash and say “fuck this lemmy bullshit” before going right back to reddit.
I’m not talking to the incoming masses, I’m replying to OP with information about how they can stop Lemmy from crashing.
Side downloading .apk files from something other than the Google Play store is shady as hell. It’s way too easy to sneak malicious code into the app that way. Even if the project is open source, I don’t have the time or the skillset to review the code to confirm it’s not malicious. No offense to the developers, but there’s no chance in hell I’m doing that for an upstart app I knew nothing about a month ago.
As a result, I’m using Lemmy via Firefox’s mobile browser right now, with Jerboa completely useless crashing the second I open it.
Hopefully they fix it soon (i.e., within the next 24 hours). First impressions matter a ton. For the masses migrating tomorrow once RIF and others shut down, Lemmy and the different apps for it will appear to be dead on arrival. If we expect any actual content on Lemmy beyond complaints about Reddit and questions about Lemmy, we need those people to migrate over.
The idea that different fediverse instances can all be on different incompatible versions is mind bogglingly dumb. The federation/decentralization design choice overcomplicates things to a huge degree. There are far more downsides than upsides to this approach. I want to like Lemmy/Jerboa, but at this point, the official Reddit app is looking more and more appealing.
I heard about the versions thing. Before this morning it was crashing a lot, but not completely unusable.
If I install from somewhere other than the play store, can I still update from the play store later, or will I have to uninstall and reinstall again? Installing from outside the play store isn’t a dealbreaker for me, but since I also have other Lemmy apps installed to use in the meantime, I’ve been figuring I’d just wait it out, if it’ll be a hassle.
Thanks for the help tho!
If I install from somewhere other than the play store, can I still update from the play store later, or will I have to uninstall and reinstall again?
I haven’t personally testing switching app stores as I have F-droid installed for other reasons and just intuitively used it from the start for jerboa. My belief though is that anytime you switch sources for an app, you’re best off uninstalling/reinstalling… and with Jerboa the worst side effect of that is having to re-login.
… but since I also have other Lemmy apps installed to use in the meantime, I’ve been figuring I’d just wait it out…
This is a perfectly reasonable choice, just wanted you to know what it took to get Jerboa doing it’s thing again. If you have other ways of using Lemmy you’re satisfied with, have at it.
Yep, happened to me too. I cleared the app cache, and was able to get back in.
