Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutmSometimes when reentering the app it puts my account between signeditn and signed out. Meaning, that I can still upvote posts and see my comments/posts but loose acces to the subscribed tab.
I find this happens when the lemmy.ml gateway times out. When it's back online and you open the app again you will magically still be signed in again
I've experienced this once as well, though I didn't gain any insights into why it happened or what could be done to prevent it. I worked around it by logging out and back in again.
This has now happened to me like 3-4 times in the last 24h. Not sure if there's something off about how the instance my account is on is managed (it's quite new), but this is happening to me a lot... and it doesn't self-recover as the other commenter experienced.
If you go to App info for Jerboa and tap Force stop to kill Jerboa's process, then when it restarts it will log in successfully again. This is a lot nicer than signing out and retyping a strong password. Still not sure what causes it, it happens to me every few hours. But killing Jerboa and letting it relog in is a useful workaround.
This is happening to me as well.
Happened to me a few minutes ago
Clearing the apps cache fixes it temporarily