Ugh, on Android (Samsung s22) can't even log in... Login form spins a bit but does nothing, user name shows on top left, subscribed communities are fetched but nothing else works (subscribed feed empty, inbox says need to login, etc. ..), restarting resets back to anonymous.
Are you trying to log in to an instance that hasn't updated to Lemmy v0.18 yet (like most of them)? Versions of Jerboa greater than 0.0.34 only support the newer Lemmy version.
Nope, Lemmy.ml
I ran into that error too, but I have no clue what causes it... I'm working on a tweaked Jerboa myself to try to mitigate the issues that annoy me the most
Would you consider submitting pull requests back to the main project to fix them for everyone?
Strange responses from server really seem to confuse jerboa. If there's high load, for example. Looking like only anonymous account is active seems to be a common result.
Yes, that's a solid option, especially since it works fine with another user I created on a different instance. I'll let it go for now and try tomorrow and see. Thanks!
Try using connect for lemmy. My experience of lemmy has increased multiple times since switching.
Strange - I created a new user on a different instance (sh.itjust.works) and that's working just fine, meaning it's something related to this specific user 🤔
Ugh, on Android (Samsung s22) can't even log in... Login form spins a bit but does nothing, user name shows on top left, subscribed communities are fetched but nothing else works (subscribed feed empty, inbox says need to login, etc. ..), restarting resets back to anonymous.
Are you trying to log in to an instance that hasn't updated to Lemmy v0.18 yet (like most of them)? Versions of Jerboa greater than 0.0.34 only support the newer Lemmy version.
Nope, Lemmy.ml
I ran into that error too, but I have no clue what causes it... I'm working on a tweaked Jerboa myself to try to mitigate the issues that annoy me the most
Would you consider submitting pull requests back to the main project to fix them for everyone?
Strange responses from server really seem to confuse jerboa. If there's high load, for example. Looking like only anonymous account is active seems to be a common result.
Yes, that's a solid option, especially since it works fine with another user I created on a different instance. I'll let it go for now and try tomorrow and see. Thanks!
Try using connect for lemmy. My experience of lemmy has increased multiple times since switching.
Strange - I created a new user on a different instance (sh.itjust.works) and that's working just fine, meaning it's something related to this specific user 🤔