We have released our first release candidate for 1.1.1 to TestFlight. This is a backend-focused update that adds compatibility with Lemmy 0.19 and cleans up some of our backend logic.

Features

  • Rewrote inbox backend. This is the biggest thing to test in this release, since we’ve implemented a completely new approach to displaying feeds that we hope to roll out across the app. There shouldn’t be any new behavior (although swipe actions should feel a tiny bit smoother), but it’s way more computationally efficient and should be easier to work with moving forwards.
  • Added Lemmy 0.19 compatibility and features (note that these features are only available on the few instances currently running 0.19 pre-release software):
    • Added option to delete posts and comments when deleting your account
    • Added cursor-based pagination, which should result in slightly more efficient page loading
  • Added context menus to search results
  • Improved “no posts found” message
  • Search bar is now always shown in the search tab
  • Added a reset button to the Widget Wizard
  • Organized app icons by creator
  • Added a new icon, “Alien Mlem,“” by Sjmarf
  • Adjusted haptic feedback
  • Improved account deletion page

Bug Fixes

  • Fixed compact comments not appropriately displaying vote status when net votes are displayed

Cheers,

The Mlem Group

  • th3dogcow@lemmy.worldEnglish
    11·
    1 year ago

    Thanks for the big update. Just noticed that links to communities using the !xxx@xxx format are not loading, and actually opening the email client. So I guess they are somehow being interpreted as email addresses. The initial exclamation mark is not the same color as the link.

    • EricOPMEnglish
      3·
      1 year ago

      Thanks for the bug report! We’ve got an update to make links easier to tap coming down the line, I’ll be sure to fix this along with it

  • Link@lemy.lolEnglish
    4·
    1 year ago

    0.19 RC.4 was working with Mlem but RC.5 broke it.

    I’m getting ‘incorrect login’ and ‘Unable to decode’ errors on previously logged accounts.

    I wish I could provide more info but I don’t have 🫤

    • EricOPMEnglish
      2·
      1 year ago

      We’ve got the fix almost through development, hoping to have it in TestFlight very soon. Thanks for your patience!

    • EricOPMEnglish
      1·
      1 year ago

      Hmm, that’s odd. Do you happen to have a message from yourself somewhere in your inbox? Those can cause some very strange behavior around read status

      • itsathursday@lemmy.worldEnglish
        2·
        1 year ago

        No though I haven’t been able to recreate it. I was able to get another bug where the badge was +1 but I had no unread messages. I was marking messages unread by swiping on the reports and then swapping between the tabs up the top, it was rather fast and rapid so not really normal use and then after closing and reopening the number reset and was calculated correctly

        • Link@lemy.lolEnglish
          2·
          1 year ago

          Interesting. My instance uses same version as SDF and its working on me after the update.

        • EricOPMEnglish
          2·
          1 year ago

          Hmm, that’s very odd. I’ve created an account on SDF and can log in without issue–I’m going to build a better bug report tool and ship it in the next beta build so we can maybe figure out what’s going on here. Thank you for your patience!

          • sqw@lemmy.sdf.orgEnglish
            2·
            1 year ago

            fwiw they updated to rc.5 and I get the same error. Green check mark briefly then the couldn’t fetch.

            • EricOPMEnglish
              1·
              1 year ago

              Thanks for the update! I’m still struggling to reproduce the bug, but making good progress on tools to let users share more detailed debug info.

              Do you happen to have two-factor authentication enabled?

              • sqw@lemmy.sdf.orgEnglish
                1·
                1 year ago

                The latest version appears to have worked for me. Mlem 1.1.1. and it looks like the server is running 0.19.0 rc11

    • EricOPMEnglish
      1·
      1 year ago

      Thanks for the report! I’ve sent a sign up request to them so hopefully I can troubleshoot this soon.