User reported in #3382562-zen and #24700040-hc
5 or 6 user reports over the last 24 hours, but seems to affect every JP and atomic site. Bumping to janitorial.
We are also getting reports of this in mobile. See https://github.com/wordpress-mobile/WordPress-Android/issues/13091
Encountered this on an Atomic site, 3384596-zen
Another report 3387580-zen
Bumping pri as well.
Noting I initially had issues reproducing it when I first encountered it. It appears that owners/admins can see and interact with comments in the Reader when it's their own site but the general public cannot.
I received a report of this in #21617350-HC. This user published a blog post talking about it and several other WordPress.com users chimed in in the comments too! https://aguycalledbloke.blog/2020/10/08/oh-i-am-textless/
Looks to have started on the 6th: Jetpack 9.0 was released on the 6th as well
URL / XHR Request / Response
https://wordpress.com/read/feeds/107218703/posts/2952355248
{"code":400,"headers":[{"name":"Content-Type","value":"application\/json"}],"body":{"error":"unknown_token","message":"Unknown Token"}}
Getting the same error in dev console with these settings:
This may be related to a recent jetpack security change. I am soliciting feedback from the jetpack team and requesting a stop-gap revert. Internal reference: p9dueE-1Zi-p2
Tested and confirmed using the following steps:
To prepare:
To test:
Results: cannot view or submit a comment and the following errors appear. (47s)
Sorry - there was a problem posting your comment.
Could not retrieve comments for requested post
Could not add a reply to this post.
Tested with WordPress.com Reader using Chrome on Pixel 3 Android 11 and leaving a comment on a WordPress.com Business site (with plugins installed) artindesignco.blog while logged in as user design5279reader.
I closed https://github.com/wordpress-mobile/WordPress-Android/issues/13091 as a duplicate as it appears this is a problem upstream and is being worked on here.
It looks like a quick revert would re-introduce a non-trivial bug, so the jetpack team is evaluating how to fix both reader and the original issue.
There's a fix for this now on prod. Thanks to @leogermani, @kbrown9, @zinigor and @kraftbj for working on this and coming up with a solution.
This user 3384521-zen reports the issue on both Android and iOS and also on desktop but not sure if the desktop app or browser. Asked and waiting for confirmation
Hi @rossanafmenezes , The fix was deployed 13 hours ago. I'm not sure in which timezone ticket comments are being displayed in zendesk but I think it's worth confirming that the issue is still happening or has been fixed but not tested again by the user.
Another report here - 3384111-zen
I can confirm comments are now working as expected for this user as well.
Closing ...
Most helpful comment
This may be related to a recent jetpack security change. I am soliciting feedback from the jetpack team and requesting a stop-gap revert. Internal reference: p9dueE-1Zi-p2