v1.0.2 rolling out to the App Store now.

  • Added a setting to mark posts as read when scrolling past them.
  • Read posts are now only hidden on refresh to stop the screen jumping.
  • Truncated the text in link preview cards to 200 characters.
  • Fixed multiple spoiler tags collapsing into a single tag.
  • Fixed marking posts as read when viewing an image.
  • Fixed image gallery not always appearing on post view.
  • Fixed positioning of community selector and + button on the composer on some devices.
  • Fixed pull to refresh indicator missing after first use.
  • Renamed Harry icon to Xander.
  • acetuk@feddit.uk
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I am hitting a few crashes on 1.0.2.

    The main All timeline crashed killing the app. Now when I open it All is empty.

    If I switch to another list (Local for example) it seems to work. But as soon as I switch back to All and try to refresh the timeline it crashes the app again.

    This is using Feddit.uk

      • steve228uk@lemmy.worldOPM
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I’ve logged into feddit.uk and can’t seem to replicate this. Are you able to let me know:

        • iOS version
        • Which view you’re using e.g. Compact/Card/Headline
        • Any other settings you may have turned on/off
        • acetuk@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          iOS 17 latest dev beta Card view

          I turned off mark read on scroll and turned on show read posts. That got the timeline back.

          Turned on mark read on scroll and that is working.

          However now selecting hide read posts is t doing anything.

          • steve228uk@lemmy.worldOPM
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            Read posts now only activates on refresh. My guess is that there’s an issue where if you’ve read everything on page 1 then it thinks the response is exhausted. I’ll fix in another patch.