Troubleshooting

Most integration issues trace back to one of four values not matching exactly: adapter class name, placementName, network key (LevelPlay), or eCPM/rate. Start with the Class & Network Key Registry before diving into logs.

Common issues

Symptom	Likely cause	Fix
No TapMind ad in production, but works in debug	Wrong/missing class string, or release-build stripping	Verify the class string matches the Registry exactly; confirm ProGuard keep-rules ship
No fill at all	`placementName` mismatch (case/space) or wrong eCPM position	Re-check `placementName` exactly; confirm waterfall position
App crashes on launch	Missing AdMob app ID in manifest/Info.plist	Add the app-ID meta-data exactly as shown on your integration page
LevelPlay network never appears	Wrong network key	Use the canonical key from the Registry

Release vs debug

If ads work in debug but not in release, suspect the class string or release-build stripping (ProGuard keep-rule confirmation — Checklist Q9).

Diagnostic logging

Filter logcat by «LOG-TAG» (currently TapMindAdapter on many integrations — confirm with your account manager).

Escalation

Contact your account manager with:

The mediation platform and framework
The adapter class name and placementName you are using
Log output filtered by «LOG-TAG»

Integration pages include partner-specific verification steps under Verify integration on each mediation page.