On this page
Start with the missing signal, then check the setup that produces it. A missing label, event or screenshot does not necessarily mean that your whole Android integration has stopped.
Applies to native Android SDK 1.2.0. Use synthetic data for diagnosis.
No visit appears
Check that:
- Your app runs on Android API 26 or later.
- The dependency is
io.cux:analytics-compose-sdk:1.2.0. - Your Application class calls
init()once with the correct mobile project token. - The merged manifest includes
INTERNETandACCESS_NETWORK_STATE. - Collection has resumed if you initialized with
needConfirmToStart = true. - The app can reach CUX through its current connection and network configuration.
- You are looking in the correct CUX project and time range.
Follow Install the Android SDK for the initial check. Do not disable certificate validation to diagnose connectivity.
Screen labels are missing
Call screen() on the main thread when the actual screen is attached, visible, focused and recognized. Calls made before that point are ignored and are not queued for a later screen.
For Compose, check monitor(actualHostView) and whether that View belongs to the correct controller. The no-argument monitor() does not establish the host for labeling.
Check for a later naming call that replaces the expected label. Use the screen guide rather than restoring obsolete sendScreen() or trackScreen() calls.
A custom event is missing
Check whether the app actually reached the handler that sends the event. Collection may be stopped or the expected success callback may not have run.
For trackEventTyped(), validate every field. One invalid name, key or value rejects the whole event. Nested objects, lists and null values are not supported. See typed event limits.
Do not log complete analytics payloads or customer data to debug an event.
Screenshots are missing or masked
Check the project's screenshot configuration and whether the sensitive region was deliberately masked. A masked WebView is expected on the mobile side of the registered bridge.
Compare several known test screens. Screenshot availability depends on configuration and capture conditions; it is not guaranteed after every tap or scroll.
If a mask is missing, correct it before testing with customer data. See Android masking.
WebView content is missing
Confirm the mobile/web project pair and compatible web collector with CUX. Check the exact HTTPS origin and register before the first loadUrl().
Check Android System WebView support for WEB_MESSAGE_LISTENER and DOCUMENT_START_SCRIPT. If unsupported, the bridge does not start, while the registered native area remains hidden.
Inspect the web project for website data. Separate mobile and web visits are expected. Follow the WebView guide.
You only see ordinary screenshots
For stitching, check the initializer's previewStitching option, CUX processing support and screen compatibility. An ordinary screenshot can be the expected fallback.
When you explicitly register preview regions, check the actual Views, first contentChanged() call, subsequent appearance notifications and registration lifetime. Do not reuse a closed or detached registration.
Uncaptured content cannot appear in the preview. Follow Configure Android preview stitching.
Some data is missing after a new visit
Pending data from a previous visit is discarded when a new visit begins. The SDK does not reassign it to the new visit. Do not expect durable, loss-free offline collection.
Record the sequence of navigation, backgrounding and connection changes that reproduces the issue. Avoid inferring the cause from one missing event alone.
Prepare a useful support report
Provide the SDK version, app build, Android and System WebView versions, affected screen, expected result and reproduction steps. Include a test time and project name or ID.
Share synthetic screenshots or redacted evidence. Do not include project tokens, customer identifiers or complete request/event payloads.