Android 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””| Cause | Fix |
|---|---|
dev.ad80.ENDPOINT is missing (ConfigInvalid: missing endpoint). | Add <meta-data android:name="dev.ad80.ENDPOINT" android: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. |
| Consent was never granted. | Call Ad80.setConsent(true) on every start, after your consent flow. |
| The SDK is disabled. | Check dev.ad80.ENABLED, 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 build’s application id differs from the app in the dashboard (for example a .debug suffix). | Uploads for another app id are refused with 403. Register that id as its own app and use its key. |
| The key was revoked. | Create a new key and ship it. |
| The device runs Android 7.x (API 24 or 25). | Capturing needs API 26 or higher. |
| The ad is never fully visible (covered by another view, partly off screen, inside a dialog, animated or transformed). | See the Capture outcomes. Register dialog and pop-up banners with Ad80.register. |
| App Startup is disabled in your app. | Call Ad80.initialize(context) in Application.onCreate(). |
Uploads are refused
Section titled “Uploads are refused”The SDK drops a batch that gets a client error and keeps retrying on server errors. Meaning of the status codes in
UploadResult:
| Status | Meaning |
|---|---|
| 200 | Accepted. |
| 400 | The batch was malformed. Make sure you use an unmodified SDK build. |
| 401 | Unknown, revoked or expired upload key. |
| 403 | The plan does not include SDK monitoring, or the app id of the build does not match the key. |
| 413 | The request was too large. |
| 429, 503 | Busy; the SDK retries later. |
Ads appear but show the network “unknown”
Section titled “Ads appear but show the network “unknown””Native ads are reported as unknown unless you register the NativeAdView with its metadata. For banners, the
network comes from the ad’s ResponseInfo; if the mediation adapter is not in the recognized list it appears as
adapter:<class name>. 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.
A full-screen ad is not captured
Section titled “A full-screen ad is not captured”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 symptom | Cause and fix |
|---|---|
SKIPPED_FULLSCREEN_NOT_TRACKED | The app did not call Ad80.trackFullScreenAd(ad) before show, or called it more than 5 seconds before the ad opened. Call it right before ad.show(activity) for every show. |
SKIPPED_FULLSCREEN_DISABLED | Full-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_AMBIGUOUS | Another ad was tracked while one was pending, or two ad activities were open. Track and show one ad at a time, and track the ad you show. |
REJECTED_UNVERIFIED_AD_WINDOW, SKIPPED_NOT_SETTLED | Google’s ad window did not pass the checks (multi-window, picture-in-picture, an unexpected view tree), or the ad closed before its opening animation settled. |
No Capture event at all | The object is not an InterstitialAd, RewardedAd, RewardedInterstitialAd or AppOpenAd (it is ignored), consent is missing, or the SDK is disabled. UNSUPPORTED_API_LEVEL means API 24 or 25. |
| The image shows something of your app | Your app or a library draws into Google’s ad activity. The SDK cannot tell it from the ad, so remove it before you track the ad. |
Still stuck?
Section titled “Still stuck?”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.