this post was submitted on 26 Jan 2024
10 points (91.7% liked)

Jerboa

10270 readers
2 users here now

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.

Built With

Features

Installation / Releases

Support / Donate

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.

Crypto

Contact

founded 2 years ago
MODERATORS
dessalines@lemmy.ml
10
Bugs I've encountered (lemmy.world)
submitted 7 months ago by n3m37h@lemmy.world to c/jerboa@lemmy.ml
15 comments fedilink hide all child comments
 

Every time I try to use the text link to URL ()[] and go to hit the "ok" button, the entire windows goes away. The work around is to hit the keyboard minimise to uncover the buttons.

Press anywhere but the keyboard and ya loose everything you type.

Another bug is when you try to paste anything in the body it pastes it at the beginning of the body regardless if where in the text you have highlighted.

Sometimes an instance will load but in unable to view comments (can't remember what it said) you need to clear the app cache to fix the issue

This is about it, otherwise this is my fav Lemmy app around.
Keep up the good work.

Ps before you ask this is the only app I've encountered these issues with

you are viewing a single comment's thread
view the rest of the comments
[โ€“] testEmailVerified@lemmy.world 2 points 7 months ago (1 children)

  1. yes, I'll make an issue for this

  2. When it wouldn't let you reply, was it showing a toast/msg that u weren't logged in?

Thanks

[โ€“] n3m37h@lemmy.world 1 points 7 months ago* (last edited 7 months ago)

Just red/orange text at the top said something along the lines of unable to find comment or something like that. All 3 accts were affected at the time.

Didn't want to relog all accts so I cleared the cache and it worked