Adsense shows an 'X-Frame-Options' to 'SAMEORIGIN' error - adsense

Recently I noticed that all my websites give an error in Chrome console (removing adsense the error goes away):
Refused to display https://googleads.g.doubleclick.net/pagead/drt/si?p=******&dpt=1 in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.
Nothing was changed, I don't use iframe, Ads is still visible. But I don't like this error, I read about youtube and maps error, but didn't find any about adsense.
What can I do to fix it?
Page of example: http://www.incinqueterre.com/en/trails-all

In my case the Google Publisher Toolbar was to blame - turning it off fixed the error.

I just started getting this error recently as well when using chrome.
From my searching around the interwebs, I found hte following information. It appears to be a bug in the webkit engine (chrome, safari, et al):
Invalid 'X-Frame-Options' header from google's Doubleclick response
https://bugs.webkit.org/show_bug.cgi?id=110857
Once Chrome (and maybe others) upgrade their version of webkit it will go away.

Related

Grey screen in Opera only using flutter web

Used flutter to build a web app, but I keep getting a grey screen in Opera. I know that this can happen with flutter if there is a UI error, but the website is working perfectly fine in Chrome, IE, Edge, and Safari. The console in developer mode gives me this error: "NoSuchMethodError: method not found: 're' on null". The "re" part of the error changes. I've seen it be "rg" and "rf", and google search has failed me when it comes to resolution. Any suggestions would be appreciated.
If you specified rendered as HTML maybe that's the reason. Please build without specifying a renderer. Just use flutter build web and try once please

CloudKit Dashboard keeps showing log in screen

Has anyone else experienced an issue where the CloudKit Dashboard will rarely log in but most of the time redirect the page back to the log in screen after you've correctly typed in all the credentials?
I can't seem to find anything on the web about it, except for this post on the Apple developer forums:
https://forums.developer.apple.com/thread/25947
I'm running a late 2011 MBP with OSX Yosemite, not sure if that will help. I've tried both Safari and Firefox.
Try using Safari. I was having this problem with mozilla firefox.
Solution: open a private browsing window and try again!

How can I fix this error in Facebook's Unity SDK Pay dialog?

I am adapting a Unity project to run in the web player, for integration with Facebook's Canvas, and specifically the FB In-App Purchase system. The conversion is nearly finished and as recent as a couple weeks ago I had verified that every possible choice under the IAP options worked perfectly and would resolve transactions correctly. However, the asynchronous payment option has suddenly begun failing with a strange error message that seems unconnected to any Unity code or the web server that was set up to host the game.
When a player selects the asynchronous payment option and clicks on confirm in the FB Pay dialog, the dialog does not close and an error is output to the debug console:
TypeError: undefined is not an object (evaluating
'window.parent.require("GamePaymentProviderIFrameFlow").processIFrame')
redirect.php
This is the error output for Safari and the other browsers give similar messages indicating that "processIFrame" is not recognized because "window.parent.require(...)" is returning an undefined reference.
Now I'm not sure where "redirect.php" actually is, but from what I've been able to gather, it looks like it's looking for and failing to find a module called "GamePaymentProviderIFrameFlow". I can't find any information on whether this is something that happens as part of the Facebook Unity SDK or something on Facebook's servers. I did find that the "require" call is most likely a part of Node.js and would therefore not be run in the player's browser, but rather on a server.
I am using Unity version 4.3.0f4 and Facebook Unity SDK version 6.2.2. I haven't touched anything with regards to the payment system in the time since it worked correctly and although I know this is no guarantee, the error doesn't seem to be happening within Unity at all. The only possibility I can think of is that some FB communication with the FB Unity SDK has begun failing due to some change in the Facebook API. If that's true, however, I don't know if there's any reasonable way to fix this other than to wait for a patch from FB.
Has anyone else encountered this or something similar or could provide any other advice on this topic?
Found a bug report on Facebook's dev site that details the exact problem I'm having. Apparently this is a known UI issue and is in the process of being addressed.
https://developers.facebook.com/bugs/145796563404096/
Guess i'll just have to wait.

Uncaught TypeError: Converting circular structure to JSON

We're using the fb:registration plugin to sign up users on our site. Today I noticed the registration redirect is no longer working in Google Chrome and Safari (latest public release). I know for sure it was working with the same code as recently as last week. It seems to be getting stuck on submission with this error, which is coming from:
static.ak.fbcdn.net/rsrc.php/v1/ys/r/ioE9qOq_5Oa.js:101
Firefox and IE have no problem, so it seems to be Webkit specific. Any ideas?
There is a bug report tracking this on Facebook's developer site.
https://developers.facebook.com/bugs/251685364894450
Please go there and tell them you are seeing this issue too.

Website Causes Mobile Safari Crash (Replicable)

For some reason http://shirazraqs.com is causing mobile Safari to crash. I've never seen anything like it and it's 100% replicatable so it's a bug on the site.
I've already tried ripping out all of the javascript but the bug persists even then.
Any other troubleshooting advice? Better yet, has anyone heard of this? I've been unable to find anyone experiencing similar problems via Google search :(
It turned out to be an issue with the new Google Fonts API. Removing the Google Fonts CSS Stylesheet got rid of the problem... Head's up Google!