But is it normal I lost my favorites?

  • RIP_Apollo@vlemmy.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I don’t know if this is expected behaviour or a bug, but I lost all my favourite subs too, so you’re not the only one who has been affected.

    I was only using the favourites feature because I wanted a way to list all the communities that I’m subscribed to. As far as I’m aware, there isn’t a way to view your subs list yet (though please correct me if I’m wrong).

    • ddnomad
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Well I’ve lost my ability to log in and the app seems to be completely broken. I guess losing your favourites is not the worst possible effect lol

      • RIP_Apollo@vlemmy.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        Oh no, sorry to hear that. Yeah I feel better about only losing my favourites now lol. Have you tried deleting and reinstalling the app?

        • ddnomad
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Yeah that’s the first thing I’ve tried. No dice. I think iOS may be caching app data even if the app is deleted, so if it’s some kind of state corruption it might not help anyway.

          I’ve opened an issue on GitHub: https://github.com/buresdv/Mlem/issues/188

          Now I wait I guess.

          • RIP_Apollo@vlemmy.net
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Hmm I didn’t think it was possible for cached app data to remain after the app has been deleted, but I could be wrong.

            I was going to suggest that maybe your Lemmy server was busy so you should try again later, but I see on your GitHub issue that you’ve tried two different instances, so that’s probably not the issue.

            I assume you’ve already tried restarting your phone, and I assume you are already using the latest version of iOS. I’m not sure if there’s any benefit to deleting and reinstalling the TestFlight app as well?

            Sorry, I think you’ve done all you can do :( I hope the Mlem devs are able to fix the issue soon.

            • ddnomad
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yeah it just does not work for me for some reason.

              Regarding caching, I vaguely recall some apps magically saving settings / login information even when deleted. Maybe it is something the developers have to opt into explicitly, or maybe I’m misremembering this. I’m 101% not an iOS dev so I have no idea.

              I’ll just wait, eventually the app will get a new update which (I hope!) unfucks it on my phone.

              • RIP_Apollo@vlemmy.net
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                Well that’s strange.

                If you happen to have another iPhone, you could use it to rule out your theory that the issue is caused by the caching.

                So if you download the Mlem app on a separate iPhone, then it shouldn’t be affected by the cache, which I assume is stored locally on your current iPhone (although I’m also not a iOS dev, so I wouldn’t know if that’s true).

      • Sinnoh@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I’m having the same problems. (Or at least, a very similar problem) After downloading the update, I couldn’t access any of my instances. The feed wouldn’t load with a generic error message “Something went wrong”.

        After deleting and reinstalling the app via Testflight all my logins were gone. Okay, that was expected. But trying to log in again, I encountered the same error message as in your Github issue across multiple instances. (https://github.com/buresdv/Mlem/issues/188)

        I hope a fix can be found for this!!