Troubleshooting

Start by running a debug build and filtering Logcat by the tag CIMKA.

Symptom	Likely cause and fix
Nothing appears in the dashboard	Look for Invalid license, license validation timed out or initialization failed in Logcat. Check the four validation fields, that baseUrl ends with /api/v1, and that the SDK is enabled for the application in the dashboard.
Could not resolve com.cimka:cimka	GitHub Packages needs a token with read:packages even for reading. Check gpr.user / gpr.key in ~/.gradle/gradle.properties.
Can’t reach a local backend from the emulator	Use http://10.0.2.2:<port>/api/v1 and set android:usesCleartextTraffic="true" (debug only).
First network calls / screens are missing	The SDK starts capturing after the license check completes, a moment after launch.
Crashes at startup aren’t reported	The crash handler is installed after initialization. Crashes in the first moments of startup are not captured.
Crashes stopped being reported after adding another SDK	Another crash handler was installed after Cimka. Initialize other crash reporters before Cimka.initialize().
Screen names look like a, b0 in release	Add -keepnames class * extends android.app.Activity to your ProGuard rules.
Dependency list is empty or has no versions	Apply the Gradle plugin and check assets/cimka_dependencies.json in the APK.
App shows a “blocked” screen	The device was blocked from the dashboard. Unblock it under the device’s sessions.
UninitializedPropertyAccessException from Cimka.application	Cimka.initialize() hasn’t been called yet.