I am a new user (actually, this is my first post on Lemmy, yay!). I registered through the web, but since my Reddit-use was mainly on my phone, I installed Jerboa (version 0.0.33 from the Play store) and everything seemed nice. I was just scrolling and saw something I wanted to upvote. So I clicked the upvote-button, but I got a message saying I needed to log in for that. Then I tried clicking a reply-button on a comment, but I got the same message.

I double checked, I am definitly logged in.

What’s going on here? Is this a known bug with a workaround I need to know or something?

  • MiddleWeigh@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Hey welcome to lemmy (it’s better here!)

    So this happened to my SO.

    Try going top left where the three lines are. Click your username to get the drop down. Go to settings and +add account, and just try to re log in.

    I believe it’s a bug, possibly hardware or OS related…and after we did that once or twice it stayed logged in.

    If that doesn’t work, lmk, I’ll ask her exactly what she did.

    I am not a tech person so bear with. But this exact thing happened to us on .33 and it hasn’t happened since.

    • The one and only@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      It’s not logging out automatically in my case. In the burger-menu on the top-left I do see my username and the communities I am subscribed to.

      Apparently, there are a couple of new developments in Lemmy that the Google Play-version is having issues with. We will have to wait for the Play store to catch up with the latest release and see if everything is solved then.

      • MiddleWeigh@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Hm. The new version is on github. I installed it today. But that same issue happened when we first migrated on the 11th. I dunno sorry I can’t be more useful to you. Are you on jerboa right now? If so it’s working, lol. So far the bugs have been just minor annoyances for me and the trade off for better discussion has been very much worth it. I’d even go so far as to say I’m enjoying the little quirks. Make me work for my social media lol.

        • The one and only@lemmy.worldOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Hahaha, no I’m not on Jerboa right now. Otherwise it would be solved indeed. I’m on my laptop, so the regular desktop-interface.

            • The one and only@lemmy.worldOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              1 year ago

              I think I will. I have to admit that I am finding out I was quite used to some of the little things Reddit does, so I will have to get used to the things Lemmy does different. I was hoping to start using the app since that has been my modus operandi, but today it crashes immediately when I start it. I see that also in the github-issue that timewarp linked to earlier.

  • John Richard@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I believe that Lemmy was updated and it has broke compatibility. Version 0.0.35 alpha is the latest version of Jerboa, but isn’t published yet on Google Play or F-Droid. When it is it should resolve the issues.

    • SanguinePar@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I’m still on 0.0.33 and it seems to be working for me - at least to make this comment and upvote yours.

      • John Richard@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        Interesting. The app immediately crashes for me but I’m on a different instance, so maybe lemmy.ml still works on v0.0.33 and it is something else. In that case I’d recommend they clear their app cache/data and re-login.