Must call google.charts.load before google.charts.setOnLoadCallback Error

@ckush thanks for the report and for the details. Are you able to provide a screen shot of the error and the browser console errors? It would be very helpful as we investigate this further.

Here is the full text of the Dashboard screen after connecting Site Kit:

Must call google.charts.load before google.charts.setOnLoadCallback
in n in div in n in div in div in n in div in n in m in Unknown in WithFilters(t) in div in div in div in n in div in n in Unknown in Unknown in Unknown in WithFilters(t) in n in n in div in div in div in div in n in a

Here are the console errors (with domain name hidden):

JQMIGRATE: Migrate is installed, version 1.4.1
admin.php?notification=authentication_success&page=googlesitekit-dashboard:2121 Mixed Content: The page at ‘https://www.[hidden].com/wp-admin/admin.php?notification=authentication_success&page=googlesitekit-dashboard’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.2/themes/smoothness/jquery-ui.css?ver=5.3.2’. This request has been blocked; the content must be served over HTTPS.
2googlesitekit-dashboard.js?ver=1.3.1:12 Error: Must call google.charts.load before google.charts.setOnLoadCallback
at Object.google.v.w.H.lo [as setOnLoadCallback] (loader.js?ver=5.3.2:317)
at new n (googlesitekit-dashboard.js?ver=1.3.1:3)
at Io (googlesitekit-dashboard.js?ver=1.3.1:12)
at Zr (googlesitekit-dashboard.js?ver=1.3.1:12)
at Is (googlesitekit-dashboard.js?ver=1.3.1:12)
at Ac (googlesitekit-dashboard.js?ver=1.3.1:12)
at Tc (googlesitekit-dashboard.js?ver=1.3.1:12)
at kc (googlesitekit-dashboard.js?ver=1.3.1:12)
at googlesitekit-dashboard.js?ver=1.3.1:12
at t.unstable_runWithPriority (googlesitekit-dashboard.js?ver=1.3.1:12)
gs @ googlesitekit-dashboard.js?ver=1.3.1:12
admin.php?notification=authentication_success&page=googlesitekit-dashboard:1 Mixed Content: The page at ‘https://www.[hidden].com/wp-admin/admin.php?notification=authentication_success&page=googlesitekit-dashboard’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.2/themes/smoothness/jquery-ui.css?ver=5.3.2’. This request has been blocked; the content must be served over HTTPS.

@ckush Thanks for the update, we’re create the following GitHub issue to keep track of this issue:
https://github.com/google/site-kit-wp/issues/1155

If possible please share any additional in your case which may assist in troubleshooting, such as your Site Health information, and whether you’ve been able to connect Site Kit previously, or with other websites.

Site Health is good; no critical issues and only recommended improvements are to remove inactive plugins and themes.

I am successfully using Site Kit on several other websites on our same server in the same environment with no issues. Doesn’t seem to be a theme incompatibility, but possibly may be related to another plugin.

I recommend you search the code to see if there is anything that can cause it to load the libraries over https://.

@ckush Thanks for providing the info, very useful. Are you in a position to test setup with other plugins temporarily deactivated, or share your site URL and we can see if there is anything we identify which may be impacting setup in this case?

Another user who encountered the same issue provide additional insights, maybe you have some of the same plugins activated.

I’m not using the plugins described in that other thread on this site. I’d rather not deactivate plugins to test. The site URL is https://www.cproducts.com.

@ckush No problem, I understand your preference not to deactivate other plugins. Are there any plugins active on that specific site that you don’t have on the other sites?

Another user who had this same problem (separate to the other report mentioned) was able to resolve it with the temporarily deactivation of another plugin, an Analytics plugin.

I don’t use the plugin described in that thread. Here is a list of plugins I use on this site that I don’t have on the others:

Envato Market: version: 2.0.3, author: Envato
Let’s Review: version: 3.1.1, author: Codetipi
SearchAzon – WooCommerce Amazon Affiliates Auto Search Plugin: version: 1.3, author: AA-Team
Simple Sitemap: version: 3.5, author: David Gwyer
TJ Custom CSS: version: 0.1.6, author: Theme Junkie
TJ Shortcodes: version: 0.1.3, author: Theme Junkie
WooCommerce: version: 3.9.2, author: Automattic
WP Link Shield Pro: version: 1.5, author: Michael Thomas
WZone – WooCommerce Amazon Affiliates: version: 13.2.0, author: AA-Team
YITH WooCommerce Compare: version: 2.3.18, author: YITH
YITH WooCommerce Wishlist: version: 3.0.6, author: YITH

@ckush Thanks for the update. Are you in a position to temporarily deactivate the other plugins you mentioned, even one by one before checking once more?

I’d rather only do that as a last resort. Have you found anything in the code yet that may be causing this, based on what I have provided previously?

@ckush thanks for the reply. In other cases, it has been a specific analytics plugin, which from your list you don’t have. We can keep your topic updated as we have more information.

Note that I just updated to the new Site Kit version released today and tried setting it up again. I still get the same error, but it is more detailed now:

Site Kit encountered an error
Must call google.charts.load before google.charts.setOnLoadCallback

in GoogleChart
in div
in Sparkline
in WithInstanceId(Sparkline)
in div
in div
in DataBlock
in div
in SearchConsoleDashboardWidgetTopLevel
in NewComponent
in FilteredComponent
in WithFilters(DashboardSearchFunnelInner)
in div
in div
in div
in Layout
in div
in DashboardSearchFunnel
in FilteredComponent
in FilteredComponent
in FilteredComponent
in WithFilters(DashboardModule)
in DashboardModules
in DashboardMain
in div
in div
in div
in div
in ErrorHandler
in DashboardApp
in ErrorHandler
in GoogleSitekitDashboard

@ckush thanks for the update! It looks like we were able to recreate this error and are working on a fix in the issue linked. We’ll update the thread when it is out.

You’re welcome. That’s great to hear! Looking forward to the fix.

@ckush we released the fix in version 1.5.0. Could you update and let us know if this is resolved for you? thank you