Memmy - An iOS client for Lemmy

2536 readers

1 users here now

View on GitHub

Join the Discord

Code of Conduct

founded 1 year ago

MODERATORS

[email protected]

teflocarbon

[email protected]

JSON Parse Error when commenting (i.imgur.com)

submitted 1 year ago by 4am to c/[email protected]

4 comments fedilink hide all child comments

When I am trying to post a comment, often times I will get this JSON error “unexpected token <”. I wonder if the call is erroring out on the server side and you’re getting an HTML error page back?

Odd thing is that 9 times out of 10, when this happens, the comment will still post. Until i discovered this, I was repeatedly hitting “submit” (since after the error you get sent right back to the comment edit dialog) and repeatedly posting! Now I can identify Memmy users by their repeat comments 😅

Is this a known issue?

I’m on lemmy.world and so it might happen more frequently for me as their servers have been going through some stuff lately…

all 5 comments

sorted by: hot top controversial new old

[–] tenth 3 points 1 year ago* (last edited 1 year ago)

I have the same issue. Sometimes comment was posted, sometimes not.

I actually had that error when submitting this comment. Keep submitting will eventually work

Edit: maybe network/instance issue??

[–] 4am 3 points 1 year ago

So, more info on this: it’s definitely when servers get slow, and if I spam the submit button, I can post my comment as many times as I can tap before the response comes back.

So when users are waiting for a UI response, they think they’ve mis-tapped and are probably hitting submit multiple times.

This is definitely a flow that needs attention since most users are probably on larger instances that are expediting periodic failures. This has the potential to be one of those “perfect storm” kind of bugs.

[–] ShunkW 1 points 1 year ago (1 children)

If the comment posted, it likely didn't fail on the backend. It likely is an error parsing the response json.

[–] 4am 1 points 1 year ago

Well that’s my point - the response isn’t JSON, it’s HTML. “<“ would always be the first character of an HTML document. Probably the 502 errors that have been plaguing the larger instances.