2 Edit: Ok back up as .79

Edit: Expired .78 because of a super annoying keyboard autofocus on the traverse page. Releasing .79 in about 5 minutes.

Hey all! Here are this version’s changes:

  • Fix infinite spinning on profile page
  • Images that also have a post body now show both
  • Fixed duplicate NSFW setting
  • Keyboard for search now includes “@” for easy access
  • Sign in/sign up screens now include “.” for easy access as well
  • Onboarding screen should render correctly on all devices
  • You can save posts now. They will be synced with your Lemmy account. You can view them on your profile page
  • All of your subscriptions will now show up and you can search through them. Also a more attractive and easy way to access them
  • Default Active search was added to settings
  • Settings was moved to profile. We will revisit this if it’s a user issue (i.e. people can’t find it, you guys don’t like it, etc.)
  • Issue with communities having an “infinite render” are fixed

We’re getting there!

Happy scrolling!

  • @gkd@lemmy.mlOPMEnglish
    1•2 years ago

    What version is it? There were some problems recently but they have been cleaned up. Are you on 0.3?

    Never mind, obviously you are on 0.3 if you have the image viewer (and yes it’s a work in progress which is why it’s rough around the edges).

    Do you have a full crash or is it showing you the little sad face?

      • @gkd@lemmy.mlOPMEnglish
        1•2 years ago

        Haha yea I saw that, oops.

        I updated the comment too, so just wondering what time of crash it is. If it’s a full crash that’s pretty odd but if you’re getting a sad face, could you send some debug logs?

          • @gkd@lemmy.mlOPMEnglish
            1•2 years ago

            I noticed something earlier today that I figured was actually just a me issue myself during development, but I suppose it could possibly be part of the problem. Weird because I have not heard anything from anyone else having issues, but I also assume that it could be because of the older device and the performance being a bit more lacking on that one (something could be taking longer to render somewhere).

            I’ve been working today on finding and fixing various performance issues, so I’ll keep a lookout for that same issue I noticed earlier and it’s possible the performance improvements will help with that crash. If it’s freezing, it’s making me think something is trying to render and might be getting “clogged up”.

            A hard crash like that too could be some sort of memory warning (although from my own testing the app rarely uses over 100 MB of memory and maxes at about 150 which shouldn’t be causing any memory issues even on some older devices). But if it’s truly a rendering issue, it might be trying to render something over and over and causing a memory leak. Thanks for pointing it out.