Thanks for reaching out and sharing our experience. This is indeed unusual, hopefully we can determine the cause.
So we can try and understand your setup better please share the following:
- Does this occur consistently, and if so when did this start occurring?
- Does this occur when checking your site from a browser incognito window?
- Can you please share your Site Health information privately via this form?
James, I did some digging and the closest thing I could find resembling this error is a typescript issue on StackOverflow.
To answer your questions:
1. Yes; I launched my site on 01/31/2021, and connected all of the Google Site Kit parameters then. I didn’t notice the issue until later in the evening when testing on the front end – as this occurs on the black admin bar on the front end while logged in. This was after the most recent plugin update on (I believe) the same day – 01/31/2021.
2. Since I am required to be logged in in order to view this asset (it’s on the WordPress admin bar while logged in as an admin), I am going to guess that I won’t see this issue while in an incognito window – which would defeat the purpose of the plugin…
3. Done.
4. Bonus. I have other, older projects on different webhosts using other domains; I will try installing Google Site kit on those to see if I can replicate the issue…
I wonder if one of the tools I’m using to keep my site running fast (aka: render blocking scripts) is causing some of the JavaScript to not render properly, which may cause it to fail in this way.
Many thanks for your thorough update. I’ll go ahead and create a GitHub isssue so we can investigate this further. In the meantime please do share whether you’re able to recreate this on another site.
2. Since I am required to be logged in in order to view this asset (it’s on the WordPress admin bar while logged in as an admin), I am going to guess that I won’t see this issue while in an incognito window – which would defeat the purpose of the plugin…
It may be worth checking from a browser incognito window. Besides browser caching there can be browser extensions that can result in such behavior. If you keep your Chrome developer tools open we can then add any additional information to the GitHub issue.
Another troubleshooting step you may wish to undertake is to use the Health Check and troubleshooting plugin, which can help rule out plugin or theme conflicts. See steps below:
- Login to your site from an incognito window
- Install and activate the Health Check & Troubleshooting plugin.
- Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
- From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
- Attempt to setup Site Kit once more
You can exit troubleshooting mode afterwards.
Just to keep you updated I’ve created the following GitHub issue:
https://github.com/google/site-kit-wp/issues/2753
Along with the text you’re performing if you could provide a screenshot or video recording of this behavior I can add it to the issue. You can use a service such as Loom or RecordIt to share a video. You can share privately if preferred using the same form previously used.
I also noticed some significant page optimisations on your site, so be sure to check for the same issue using the Health Check and Troubleshooting plugin. Let me know if you have any questions on this.
Hi, I’ve added a video capture to the GitHub issue.
I’m “at work” now – so I’ll dig through some of the other items as I have time throughout the day today.
Appreciate you going to the time to create the video. Please do share whether you encounter the same using the Health Check & Troubleshooting plugin, once time allows.
@s-234 I’ll close this topic with the issue no longer occurring as per details provided in the related GitHub issue.
Should the issue persist once more feel free to reopen of share details here or on GitHub. We’ll also try and recreate the issue should this require any modification to the plugin.
If you have a moment free please share your thoughts on using Site Kit so far, we welcome all feedback.