Wordpress-ios: The operation couldn’t be completed. (WordPressKit.WordPressComRestApiError error 7.)

[loremattei]

Sentry Url: https://sentry.io/share/issue/9ff043231d4c4b978ff53ddb3c367c3b/

User Count: 27
Count: 122
First Release: 14.6.0.0
First Seen: 2020-04-08T16:22:24Z
Last Release: 14.6.0.3
Last Seen: 2020-04-21T14:10:23Z
24 Hours: 97
30 Days: 122

The operation couldn’t be completed. (WordPressKit.WordPressComRestApiError error 7.)

[yaelirub]

Triage: Priority high by version.
Seems to be an issue in PreviewWebKitViewController or WebKitViewController
@bjtitus , would you mind taking a look at this?

[bjtitus]

It seems like the unknown WordPressComRestApiError comes from the Atomic authentication service (added in https://github.com/wordpress-mobile/WordPress-iOS/pull/13712) when it fails to fetch a cookie from the API. I tried on my own ephemeral atomic site and was unable to reproduce the issue.

@yaelirub Is there anyone familiar with the atomic stuff who might be able to take a look or provide some tips?

[yaelirub]

Thanks so much for looking into this. I hope @aerych might be able to provide some help on this crash 🙏

[bjtitus]

Here are a few updates on this from my investigation over the last few days:

• I was able to reproduce this error 100% of the time on a wordpress.com atomic site.
• To be clear, this is NOT a crash but is an error logged whenever the atomic proxy cookie fetch fails.
• I was unable to reproduce user facing bugs related to the cookie failure. The frame-nonce query parameter allows private page and post previews to be shown without the cookies. I'm not sure if there are cases where that parameter does not work. I think this also explains why the PR review showed no issues (https://github.com/wordpress-mobile/WordPress-iOS/pull/13712).
• My best guess is that the required Jetpack xmlrpc method (getReadAccessCookies) isn't available on all instances yet.

Details

Can reproduce by:

• Setting up an Atomic Site on WordPress.com
• Attempting to view any page or post preview on the blog.

Kibana/logstash shows the following logged from the cookie request:

"url": "/wpcom/v2/sites/170037822/atomic-auth-proxy/read-access-cookies?_locale=en",
"@version": "1",
"message": "Auth failed: server error. requested method jetpack.getReadAccessCookies does not exist.",

Notice the requested method jetpack.getReadAccessCookies does not exist

[aerych]

Thanks for wrangling this @bjtitus :)

My best guess is that the required Jetpack xmlrpc method (getReadAccessCookies) isn't available on all instances yet

Atomic privacy was rolled out to only a % of users so I think you're probably right here. I'd expect this error to go away once its rolled out to everyone.

[frosty]

Thanks @aerych! @bjtitus, let's make a note to re-review this after full support has been rolled out.

[designsimply]

Events in the last 90d: 41,000
Events in the last 11d for 14.9: 48 in 14.9 since it was released on 2020-06-01
Users affected in the last 90d: 3,800
_{https://sentry.io/share/issue/9ff043231d4c4b978ff53ddb3c367c3b/}

Closing as resolved because these seemed to have stopped as of Jun 8 according to the 90-day graph for issue.id:1603264909. 🎉

[designsimply]

Heads up, we're still seeing this error happen ~300 times per day in Japanese (looks like it's logged as a separate issue in Sentry). @frosty should I open a separate GitHub issue for this one? I'm not 100% sure how to prioritize since it's logging errors and not fatals/crashes.

操作を完了できませんでした。（WordPressKit.WordPressComRestApiErrorエラー7）

Errors in the last 90d: 58,000
Users affected in the last 90d: 5,600
^{https://sentry.io/share/issue/3da4662c65224346bb3a731c131df13d/}

[aerych]

I've dug into this a bit. The issue looks like a server side matter. There is some expected jetpack functionality that is missing for some reason and this results in an error being returned for the user. ~I'll post findings and update this comment with a reference.~ More info here: pbMoDN-Cn-p2