I see this error almost every time I open the comments on a post.

My server is lemm.ee. Does it not support the “mark as read” feature?

all 10 comments

sorted by: hot top controversial new old
[–] 6 points 2 years ago (3 children)

This should be resolved now, I just updated to v0.4.1.11 on TestFlight, and submitted a new release to the AppStore review as well.

Please let me know if you are still having issues after updating, or if you encounter any other API issues with the latest Lemmy release.

  • source
  • hideshow 3 child comments
  • [–] 3 points 2 years ago (1 child)

    Thanks for the quick turn around!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 2 years ago

    No problem! I had hoped to have API support updated before Lemmy 0.19.4 started deploying, but I missed the mark. I’ll push another update soon with support for the rest of the additions in 0.19.4, this seems to have been the only breaking change in this release.

  • source
  • parent
  • [–] 5 points 2 years ago

    Thanks for the heads up, this is due to API changes in Lemmy v0.19.4. I just fixed this and I’ll be rolling out an update today.

  • source
  • [–] 1 point 2 years ago (4 children)

    I just started getting the same errors. I’ve been meaning to make a post about it as well.

  • source
  • hideshow 4 child comments
  • [–] [S] 2 points 2 years ago (3 children)

    And you’re also on lemm.ee.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 years ago (2 children)

    Might be worth cross posting to their support community. https://lemm.ee/c/support

  • source
  • parent
  • hideshow 2 child comments