Skip to content

Android SDK: Test your integration

  1. On Apps and SDK, select your app. Connection check shows Waiting for first upload once the app has an upload key.
  2. Build and run your app with the SDK on a device or emulator (Android API 26 or higher).
  3. Make sure your code calls Ad80.setConsent(true) (after your consent flow).
  4. Open a screen that shows an ad and leave the ad fully visible for a few seconds.
  5. The page checks every few seconds. When the first upload arrives it shows Receiving ads and Last upload …. The ad appears under Creatives soon after.

Google’s test ad units work: the SDK captures test ads like any other ad.

Before starting the app, turn on verbose SDK logs and filter for the tag AD80:

Terminal window
adb shell setprop log.tag.AD80 DEBUG
adb logcat -s AD80

Ad80.addDiagnosticsListener reports what the SDK does: initialization, discovery, capture outcomes, queueing and upload results. Events arrive on an SDK background thread; return quickly. Diagnostics are informational, not proof that an ad was stored.

import android.util.Log
import dev.ad80.core.Ad80DiagnosticsListener
import dev.ad80.core.Ad80Event
import dev.ad80.sdk.Ad80
val ad80Log = Ad80DiagnosticsListener { event ->
when (event) {
is Ad80Event.ConfigInvalid -> Log.w("MyApp", "AD80 config invalid: ${event.reason}")
is Ad80Event.Disabled -> Log.i("MyApp", "AD80 disabled: ${event.reason}")
is Ad80Event.Capture -> Log.d("MyApp", "AD80 capture ${event.placementId}: ${event.outcome}")
is Ad80Event.UploadResult -> Log.d("MyApp", "AD80 upload HTTP ${event.httpStatus}, retry=${event.willRetry}")
else -> Log.v("MyApp", "AD80 $event")
}
}
Ad80.addDiagnosticsListener(ad80Log)
// Later, for example in a debug screen's onDestroy:
Ad80.removeDiagnosticsListener(ad80Log)
EventMeaning
InitializedThe SDK started.
ConfigInvalid(reason)The manifest entries are missing or wrong (missing publisher key, missing endpoint, malformed endpoint, cleartext endpoint must be loopback, unsupported endpoint scheme). The SDK stays inert.
AdMobUnavailableThe Google Mobile Ads SDK is not in the app; only registered views are observed.
Disabled(reason)LOCAL (setEnabled(false)), REMOTE (remote configuration), MANIFEST (dev.ad80.ENABLED=false) or CONSENT_REVOKED.
Discovered(placementId, source)An ad view was found, registered, or tracked as a full-screen ad (source is ADMOB_DISCOVERED, EXPLICIT or FULLSCREEN_TRACKED).
DiscoveryTruncated(nodesVisited)A very large view tree was only partly searched.
PlacementRemoved(placementId)An ad view went away.
Capture(placementId, outcome)The result of one capture attempt (see below).
ObservationQueued(...)An observation was queued, with its placement, content hash, network id, trigger and whether it carries the image.
UploadResult(batchId, attempt, httpStatus, willRetry)The result of an upload attempt.
QueueDropped(count)Queued observations were dropped (queue full or retries used up).
OutcomeMeaning
CAPTUREDThe ad was captured.
SKIPPED_NO_CONSENT, SKIPPED_DISABLED, SKIPPED_BACKGROUNDNo consent, SDK disabled, or the app is in the background.
SKIPPED_NOT_VISIBLE, SKIPPED_PARTIALLY_VISIBLE, SKIPPED_OCCLUDED, SKIPPED_NO_WINDOW_FOCUS, SKIPPED_VISIBILITY_UNVERIFIED, SKIPPED_NOT_LAID_OUTThe ad was not fully, verifiably visible.
SKIPPED_UNCHANGED, SKIPPED_RATE_LIMITEDNothing new to capture, or captures are being throttled.
ATTRIBUTION_PENDINGWaiting briefly for the network attribution.
DISCARDED_GEOMETRY_CHANGEDThe view moved or changed during the copy; it is captured again.
FAILED_PIXEL_COPYThe system could not copy the pixels.
UNSUPPORTED_API_LEVELAPI 24 or 25.
UNSUPPORTED_SECURE_WINDOWThe window has FLAG_SECURE.
UNSUPPORTED_SURFACE_VIEWSurface content that could not be captured.
REJECTED_TOO_LARGE, REJECTED_SIZE_MISMATCHThe image was too large (for a registered view, it would fill the whole window) or did not match the view.
REJECTED_UNVERIFIED_AD_WINDOWFull-screen: Google’s ad window did not pass the checks in any sample of the show (for example in multi-window or picture-in-picture), so there is no image.
SKIPPED_NOT_SETTLEDFull-screen: the show ended before a usable picture was available.
SKIPPED_FULLSCREEN_NOT_TRACKEDA Google ad activity opened without a matching Ad80.trackFullScreenAd call. A diagnostic only; never an image.
SKIPPED_FULLSCREEN_AMBIGUOUSThe tracked show could not be tied to exactly one ad activity (another ad was tracked while one was pending, or two ad activities were open). No image.
SKIPPED_FULLSCREEN_DISABLEDFull-screen capture is switched off in the remote configuration.