• In basic setup or Google Site Kit I cannot get past the first step. Here is the error message:

    Cannot destructure property 'navigateTo' of '(0 , l.useDispatch)(...)' as it is null.
    
        at AuthenticatedPermissionsModal (https://2traveldads.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-main-dashboard-44773830b675408099f9.js:57:2327)
        at PermissionsModal (https://2traveldads.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-main-dashboard-44773830b675408099f9.js:57:3549)
        at ErrorHandler (https://2traveldads.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-main-dashboard-44773830b675408099f9.js:57:492)
        at ThemeProvider (https://2traveldads.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-ede245d1199e7bd6a405.js:1:95124)
        at Root (https://2traveldads.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-main-dashboard-44773830b675408099f9.js:57:3837)
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @2traveldads. Hopefully with a little bit of troubleshooting, we’ll be able to identify the cause and ensure Site Kit works as expected without encountering this error, which I suspect is as a result of a conflict with a third party plugin or host impacting the Site Kit dashboard. To start, please share the following:

    1. Your Site Health information. You can use this form to share privately if preferred.  
    2. When checking the Site Kit dashboard from a Chrome browser incognito window does the same occur? If so, please share any browser console errors that appear.  This can help indicate a browser or caching related block.
    3. Does this error appear consistently when you access the Site Kit dashboard, or was this a one time occurrence, or is it reproducible based on any action you perform on the dashboard?

    Let me know if you have any questions with the above. This also looks like a recent support topic whereby it was a host related block, although in your case once we have the above information we can run more checks or try to pinpoint the cause.

    Plugin Support James Osborne

    (@jamesosborne)

    I’m just following up with you to check whether the error remains? If so please share the information requested above and we can investigate further.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.