Skip to content

iOS SDK: Troubleshooting

Start with the debug logs and the diagnostics listener; they usually name the cause.

The connection check stays on “Waiting for first upload”

Section titled “The connection check stays on “Waiting for first upload””
CauseFix
AD80Endpoint is missing or empty (configInvalid: missing endpoint).Add the AD80Endpoint key to Info.plist with the value https://api.ad80.dev.
The upload key is missing or mistyped (configInvalid: missing publisher key, or uploads answered 401).Copy the key again from where you stored it. If it is lost, create a new upload key and revoke the old one.
The Info.plist values come from build settings that are not set (for example $(AD80_PUBLISHER_KEY) resolves to nothing).Set the build settings for the build configuration you run.
Ad80.start is never called (no AD80 events at all).Call it first in application(_:didFinishLaunchingWithOptions:), before the first ad view appears.
The SDK was started without the Google Mobile Ads integration (adMobUnavailable).Use Ad80.start(integrations: [Ad80GoogleMobileAds.integration]), or [AD80GoogleMobileAds startAD80] in Objective-C.
Consent was never granted (SKIPPED_NO_CONSENT).Call Ad80.setConsent(true) on every start, after your consent flow.
The SDK is disabled.Check AD80Enabled in Info.plist, calls to Ad80.setEnabled(false), and the disabled(...) diagnostics.
Your organization is on the Free plan.The remote configuration keeps the SDK idle and uploads are refused. See Plans.
The bundle identifier of the build differs from the app in the dashboard (for example another identifier per build configuration).Uploads for another app id are refused with 403. Register that identifier as its own app and use its key. See Apps and keys for what an app id may contain: a bundle identifier with a hyphen is not accepted today.
The key was revoked.Create a new key and ship it.
The ad is never fully visible (covered by another view or window, partly off screen, in a window above the normal level, animated or transformed, or its scene is not active).See the capture outcomes. Register views the SDK cannot find with Ad80.register.
You test with a native test ad and see SKIPPED_OCCLUDED.Google’s validator panel on native test ads still counts as a covering view in SDK 1.0.0. See Supported ads and networks.

The SDK drops a batch that gets a client error and keeps retrying on server errors. Meaning of the status codes in UploadResult:

StatusMeaning
200Accepted.
400The batch was malformed. Make sure you use an unmodified SDK build.
401Unknown, revoked or expired upload key.
403The plan does not include SDK monitoring, or the app id of the build does not match the key.
413The request was too large.
429, 503Busy; the SDK retries later.

Ads appear but show the network “unknown”

Section titled “Ads appear but show the network “unknown””

For banners the network comes from the ad’s responseInfo, and for native ads from the responseInfo of the view’s nativeAd. If the mediation adapter is not in the recognized list it appears as adapter:<class name>; an ad whose responseInfo has no loaded adapter yet is unknown. See Networks.

Ads appear as “Not classified: monthly allowance reached”

Section titled “Ads appear as “Not classified: monthly allowance reached””

Your plan’s monthly monitored-impression allowance is used up. Uploads are still accepted and counted, but new sightings are not checked until the next period. See Plan.

An ad appears only once although it shows all day

Section titled “An ad appears only once although it shows all day”

That is intended: each image is uploaded once per network per 24 hours, and later sightings in the same placement are sent at most once per 24 hours.

Interstitial, rewarded and app open ads are captured only for the shows your app tracks. Look for the Capture outcome of the show in the diagnostics:

Outcome or symptomCause and fix
SKIPPED_FULLSCREEN_NOT_TRACKEDThe app did not call Ad80.trackFullScreenAd(ad) before presenting, or called it more than 5 seconds before the ad opened. Call it right before ad.present(from:) for every show.
SKIPPED_FULLSCREEN_DISABLEDFull-screen capture is off: the app’s Full-screen ad capture switch in the dashboard, or capture or the SDK paused for the app (for example on the Free plan, or when the allowance is used up). An owner or admin can switch it on; the app picks the change up the next time it fetches its configuration.
SKIPPED_FULLSCREEN_AMBIGUOUSTwo ads were tracked or shown at once. Track and present one ad at a time.
SKIPPED_NOT_SETTLEDThe ad closed before its opening transition finished and no usable picture was available.
No capture event at allThe object is not an InterstitialAd, RewardedAd, RewardedInterstitialAd or AppOpenAd (it is ignored), consent is missing, or the SDK is disabled. Another possibility: Google’s full-screen view controller is recognized by its class name, GADFullScreenAdViewController, and a Google Mobile Ads version that uses another class is not captured.
The video area of the image is blackKnown limit: video areas of full-screen ads can come out black on a real iPhone.
The image shows something of your appYour app or a library adds content to Google’s ad view or draws over the ad. The SDK cannot tell it from the ad, so remove it before you track the ad.

Write to contact@ad80.dev with the app id, the SDK diagnostics around the problem and the time it happened. Never send your full upload or API keys; the key prefix is enough.