But is it normal I lost my favorites?

  • RIP_Apollo@vlemmy.netEnglish
    1·
    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@infosec.pubEnglish
      1·
      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.netEnglish
        1·
        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?

          • RIP_Apollo@vlemmy.netEnglish
            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.

      • Sinnoh@lemmy.mlEnglish
        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!!