Features

  • Enabled PieFed 1.4 features:
    • Filter comment search by instance
    • Sort comments by controversial
  • Error toast timeout can now be adjusted (Settings → Advanced → Developer)

Bug Fixes

  • Sending messages from external instance admin list no longer causes an error
  • Fixed gaps appearing between certain link posts in feed
  • The send message button no longer creates duplicate messages if tapped while a message is sending

We have also made significant backend changes to how we handle posts and comments, so if you see any unexpected new behaviors, please let us know!

  • Sjmarf@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Hi, thanks for letting us know. Unfortunately I can’t reproduce this issue at the moment; reporting works for me :(

    Next time you see this issue, could you please tap on the error popup and copy-paste the error message here? You can also go to Settings -> Developer -> Error Log to see all errors since the app was opened.

    • tyler@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      30 days ago
      Optional(Response error: couldnt_create_report with status 400) (Mlem/ReportEditorView.swift, send():81)
      
      • Sjmarf@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        29 days ago

        Thanks. Is your report reason quite long? There’s a maximum limit of 200 characters, it seems. If that’s not it, I’ve got no idea what’s causing this :(

        • tyler@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          29 days ago

          Is there any way to get more in depth logs? I could also try and build and install a dev build on my device, but I actually haven’t done that before so it might take me a while

          • Sjmarf@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            29 days ago

            Unfortunately, there isn’t :( Lemmy is returning an error message back to us, so we can’t look any deeper without having access to the server logs. Usually a 400 status indicates that we’re sending the request wrong.

            Having an exact post/comment and report reason that this error occurs with would be helpful, though I understand you might not want to share that information.