google / site-kit-wp

Site Kit is a one-stop solution for WordPress users to use everything Google has to offer to make them successful on the web.
https://sitekit.withgoogle.com
Apache License 2.0
1.23k stars 279 forks source link

"Looks like your site is not allowed access to Google account data" error, despite no changes made #9233

Open jamesozzie opened 3 weeks ago

jamesozzie commented 3 weeks ago

Bug Description

There have been multiple reports since 22nd Aug of users encountering the below error on both the Site Kit dashboard and the widget on the main WP dashboard: Looks like your site is not allowed access to Google account data and can’t display stats in the dashboard

This occurred for users without any apparent changes at site level. This also occurred on the oi.ie site, despite no changes made to the site from when it occurred. Redoing the plugin setup on this site resulted in the following error - which is what others in the support forums also reported: Error: bad request, invalid parameter ‘site_id’

While disconnecting my Google account on the oi.ie site and connecting once more did restore the site with all data intact, resetting the plugin is a confirmed resolution for those impacted - although more drastic and to be avoided in favor of disconnecting.

Given there is a large influx of Analytics reporting related topics, I'll review and add to this issue if needed, adding reports of the same error.

Impacted users

image

Screenshots

Additional Context


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation Brief

Test Coverage

QA Brief

Changelog entry

eugene-manuilov commented 2 weeks ago

@jamesozzie, I believe this issue will be solved when we push updates later this week.

jamesozzie commented 2 weeks ago

Good to know. Thank you @eugene-manuilov. I'll keep it open until then.

aaemnnosttv commented 2 weeks ago

@eugene-manuilov can you confirm this is resolved now?

adamdunnage commented 3 days ago

We have received another report of this error in the support forum (see here). I still need to gather further information from the user and will update here once I have it.

@eugene-manuilov Is it possible that this wasn't completely fixed with the service deployment 2 weeks ago?

eugene-manuilov commented 3 days ago

@adamdunnage, yes, looks like there still a problem that we need to address. I'll talk to Felix to discuss one idea that I want to do next to solve that problem.