JonZavala

Thank you very much for helping me solve it. I have been using Rank Math for a year now and had no problem with the thumbnail image until yesterday. It has been resolved.

Thank you very much!

Rank math also asks me for access to Analytics, can that cause a conflict?

I put all this conflict to rest. Hours later, I noticed that I could already access Site Kit, and it asked me to reconnect. At the end of the process, another error was thrown (attached link with screenshots).

https://drive.google.com/drive/folders/1UrsJBzmbXPGvSz6AyC9cLntU4sp1yiQz?usp=sharing

I did the process in incognito mode with “Health Check & Troubleshooting” and it allowed me to do it.

At the moment SiteKit is working.

Do you think that some plugin has caused me a conflict?

I tried to restart Site Kit and I get an error. I uninstalled Site kit and installed it again and the error continues.

I started having the problem a week ago.

Reset Site Kit and the error continues, it does not allow me to connect anything. I uninstalled Site kit and installed it again and the error continues.

I started having the problem a week ago.

I have tried incognito mode and the same error appears.

Thanks for the answer.

I cannot access any part of Site Kit, even with the Health Check & Troubleshooting plugin active and following the instructions.

If I try to view connected services, I get the following error.

An error occurred while running 'mapSelect': Cannot read properties of null (reading 'isUsingProxy')
The error may be correlated with this previous error:
TypeError: Cannot read properties of null (reading 'isUsingProxy')
    at Object.current (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-settings-0a2f347d796f5c4f3d1a.js:1:35485)
    at e (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:87577)
    at https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:87686
    at Ui (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:723638)
    at va (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:746561)
    at t.unstable_runWithPriority (https://lookingback.com.mx/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:766184)
    at Mr (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:691290)
    at Yj (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:742990)
    at Lj (https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:733350)
    at https://example.com/wp-content/plugins/google-site-kit/dist/assets/js/googlesitekit-vendor-47a88efce259222be7fe.js:7:691581

Original stack trace:

    in CurrentSurveyPortal
    in RestoreSnapshots
    in ErrorHandler
    in Root

At https://analytics.google.com/ I can see my statistics.

Thanks for answering. I have submitted the health information from my site.

The message appears on the Site Kit dashboard. Another error message appears on the top bar (under each entry).

A few weeks ago I switched to GA4.

Thank you for the info, @frenchomatic. ??

You’re right, @frenchomatic. I should write: my web don’t load in AMP mode in mobile devices or something like that.

PS. Excuse my english.

Thank you, @ahmedkaludi.

Hi, @ahmedkaludi

If I see any post in muy PC adding /amp/ in the URL I can see it correctly, but in my smartphone looks without AMP.

I installed AMP for WP, but on my smartphone my page looks just like on the computer. I installed it on another page and it works perfectly.

Put this in your Custom CSS

#wrapper {
background: none repeat scroll 0 0 transparent;
}
.header {
background: none repeat scroll 0 0 transparent
}
.content {
background: none repeat scroll 0 0 #fff;
}