“Failed to mark post as read” errors
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?
Syndicated from the fediverse. Read and engage on the original instance.
View original on lemm.eeView original on lemm.ee
10 replies
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.
I’m on 0.4.1.11 now and so far it appears fixed.
Thanks for the quick turn around!
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.
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.
I just started getting the same errors. I’ve been meaning to make a post about it as well.
And you’re also on lemm.ee.
Might be worth cross posting to their support community. https://lemm.ee/c/support
Good advice.
@[email protected], this appears to be a change in the API for marking a post as read. See the reply in my cross-post.
As a workaround I turned off the “Mark Read” settings in Settings → Content Settings.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: ![email protected]