Wp-calypso: Plugins: getting plugins error and showing install again after success

[rralian]

I went through the install process correctly, got the success message (I definitely saw the green success message). But I left the page open, and eventually it triggered an error message, and then the page updated to show me the install button again.

Then if I refresh the page it appears correctly.

/cc @apeatling @roundhill @drw158

[apeatling]

@roundhill Any thoughts on who could look at this one? Is it related to your guys work on AT so far?

[lamosty]

@apeatling please have a look at the referenced issue. I'm just working on that and we'll see (early next week) whether it helped with this issue or not.

[roundhill]

Is it related to your guys work on AT so far?

This looks like it is well after the initiate flow, but we can certainly have a look if @lamosty's patch doesn't fix this.

[lamosty]

This looks like it is well after the initiate flow, but we can certainly have a look if @lamosty's patch doesn't fix this.

Short news: my patch unfortunately doesn't fix it and I'm still getting occasional Error fetching plugins on <site> errors after installing a plugin in Calypso (=> doing an AT).

[roundhill]

my patch unfortunately doesn't fix it and I'm still getting occasional Error fetching plugins on

Yeah, I'm seeing the same. Sometimes it works fine, sometimes not and I see the error and it takes a good while for it to start working with any API request. Anecdotally, it seems to happen more frequently when a site has a lot of content.

[rralian]

@artpi Do you think you could look into what's happening here? Dan says he's seeing a 400 response in the network tab when this is happening.

[roundhill]

Dan says he's seeing a 400 response in the network tab when this is happening.

Here's the error:

{"code":400,"headers":[{"name":"Content-Type","value":"application\/json"}],"body":{"error":"jetpack_error","message":"The Jetpack site is inaccessible or returned an error: server error. requested method jetpack.jsonAPI does not exist. [-32601]"}}

I think I just came across the same issue with a theme upload, so I don't think this is isolated to just the plugin flow.

[rralian]

@artpi Both @roundhill and I have been able to recreate these errors. I believe the 400 errors indicate that the Jetpack connection has not fully been established somehow. In both cases, the transfer was interrupted before wpadmin-auto-login was able to take effect. In one of Dan's cases it seemed that a sites-list operation interrupted the transfer process. In the second one it did not (not sure what happened there). But in my transfer it was definitely interrupted because jetpack-sync was stalled. It was then kicked off manually, but I was no longer in the tab that had started it. In each of these cases visiting wp-admin for the affected site seemed to resolve the 400 errors we were getting in Calypso.

[alisterscott]

I saw this error on a fresh AT site transfer test. The plugin did seem to install, but the site didn't get an AT complete sticker, so it's not labelled as an AT site in RC.

[stale[bot]]

This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week.
If you would like it to remain open, can you please you comment below and see what you can do to get things moving with this issue?
Thanks! 🙏

[lamosty]

This is already fixed long time ago. :)