• Resolved apolloautospa

    (@apolloautospa)


    Minified React error #152; visit https://reactjs.org/docs/error-decoder.html?invariant=152&args[]=GoogleTagIDMismatchNotification for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

    in GoogleTagIDMismatchNotification
    in Notifications
    in Header
    in DashboardMainApp
    in DashboardEntryPoint
    in RestoreSnapshots
    in ErrorHandler
    in ThemeProvider
    in StrictMode
    in Root

    Of note, Site Kit was disconnected from Google, out of the blue.
    Came home to check data, boom, no Site Kit, no google.
    Reconnected it, got the error above.

    Anyone understand the potential cause(s)
Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter apolloautospa

    (@apolloautospa)

    The resolution was:
    code snippets were turned on for google tag manager, which created a dual event due to using GTM4WP plugin.
    Turned off code snippets, no more error

    Thread Starter apolloautospa

    (@apolloautospa)

    nope, spoke too soon. Repeatedly tested the Site Kit dashboard, error remains.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @apolloautospa, and appreciate you sharing the additional insights. To troubleshooting this, please share the following:

    1. Your Site Health information. You can use this form to share privately if preferred.  
    2. Does the same occur if you temporarily deactivate key metrics within your Site Kit configurations (Site Kit > Settings > Admin settings > Display key metrics in dashboard)?
    3. 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. 

    Once we have the above, we can advise on this further. I suspect you may have a third party plugin active that’s impacting the Site Kit dashboard, or somethings regarding your key metrics isn’t working as expected.

    Let me know if you have any questions with the above. Thank you.

    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.

    Thread Starter apolloautospa

    (@apolloautospa)

    it cleared itself up.
    No idea on how.

    Thread Starter apolloautospa

    (@apolloautospa)

    Ok, did a full reset and now it works just fine.

    For now.

    • This reply was modified 5 months, 3 weeks ago by apolloautospa.
    Plugin Support James Osborne

    (@jamesosborne)

    Glad to hear it @apolloautospa, appreciate the update. Be sure to reach out should you encounter any further issues.

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

You must be logged in to reply to this topic.