Failed receiving interstitial with error Error Domain=com.google.ads Code=1 "Request Error: No ad to show." UserInfo=0x1940c260 {NSLocalizedDescription=Request Error: No ad to show., NSLocalizedFailureReason=Request Error: No ad to show.}
September 1st: normal number of request.
September 2nd: drop in the 30% range in total number of requests.
September 3nd: also a drop in the 30% range in total number of requests.
Econ, ctr,...they all stay in the same values as usual so the impact on revenue is also in the 30% range for the last two days.
Can we try to help AdMob isolate the issue? Could someone confirm if they are experiencing the issue for non-legacy ad units?
So far based on the posts all impacted ad units are legacy. Including all my ad units where I see a consistent 30ish% drop in requests since September 2.
Thanks,
Diego.
As previously announced, we started to sunset the legacy AdMob system this week and completed the process on 2 September. For a limited time, this led to some unexpected behavior resulting in ads not serving for apps containing older versions of the Google Mobile Ads SDK for iOS (version 6.5.1 and below) and Android (version 6.4.1 and below). Publishers using these older SDKs on both the legacy and new AdMob platforms, DoubleClick for Publishers, and Ad Exchange In-App, were affected by this issue.
Our engineering team identified the problem quickly and worked to restore the service within hours. We apologize for any ad serving outage you may have experienced during this time.
Still not see a recovery from this.
Anyone else?