Live Updates troubleshooting

The SDK reports each dropped Live Update, and each notification that cannot be promoted to a Live Update, as a diagnostic event on the Mobile Core event hub. Inspect these events with Adobe Experience Platform Assurance, together with the verbose logs (MobileCore.setLogLevel(LoggingMode.VERBOSE)).

data-variant=info

data-slots=text

Diagnostic events

Event data

The two dispatchers place the reason code in different keys.

Events from the Live Updates SDK

Every reason except no_plugin comes from the Live Updates SDK. The event data holds an xdm object with the same shape as the Live Update tracking events:

{
   "xdm": {
      "eventType": "liveUpdateTracking.renderError",
      "pushNotificationTracking": {
         "pushProvider": "fcm",
         "pushProviderMessageID": "order_1234"
      },
      "_experience": {
         "customerJourneyManagement": {
            "messageProfile": {
               "channel": {
                  "_id": "https://ns.adobe.com/xdm/channels/liveactivity"
               }
            },
            "pushChannelContext": {
               "platform": "fcm",
               "liveActivity": {
                  "liveActivityID": "order_1234",
                  "channelID": "order_1234",
                  "event": "outdated_timestamp"
               }
            }
         }
      }
   }
}

When the push carries _xdm, its contents (such as _experience.customerJourneyManagement.messageExecution) are also copied into xdm, so the event identifies the originating campaign or journey. The event is reported even when the push has no _xdm.

Event from the Adobe Journey Optimizer extension

The Adobe Journey Optimizer extension reports no_plugin, because the Live Updates SDK never receives the push. Its event data is:

Render errors

Reported as Live Update Render Error. Dropped means no notification is posted, no tracking event is sent, and no listener callback is called.

A push whose adb_liveupdate_data value is not valid JSON, or is missing a required field, is dropped with a warning log and no diagnostic event.

Incompatibility issues

Reported as Live Update Incompatible. None of these drop the Live Update: the notification is posted as a standard ongoing notification instead of a promoted Live Update. See Promotion to a Live Update, and Live Updates in the Android documentation for the promotion requirements.

Use the events in a rule

Because the events are dispatched on the event hub, a rule can match them for processing on the device:

• Match the event with ~type equal to com.adobe.eventType.messaging and ~source equal to com.adobe.eventSource.errorResponseContent.
• Read the reason from xdm._experience.customerJourneyManagement.pushChannelContext.liveActivity.event for events from the Live Updates SDK, or from subcategory for no_plugin.

Nested keys are matched by their flattened, dot-separated path. See Event data key flattening in the Rules Engine technical details.

Local start is reported only after a push

A Live Update raised with triggerLocalLiveUpdate and EVENT_TYPE_LOCAL_START is posted and calls onStart, but no tracking event is sent at that point, because a local start has no _xdm to tie it to a campaign or journey. The SDK records the local start and reports it later, when a push from Adobe Journey Optimizer arrives that:

• has the same notification_id and notification_channel_id as the local start,
• has an event_type of start, update, or end,
• has a newer timestamp (epoch seconds) than the local start,
• passes your interceptor, and
• carries _xdm.

The SDK then sends two liveUpdateTracking.received events back to back, both carrying that push's _xdm:

1. liveupdate_localstart, stamped with the time of the local start.
2. The push's own event: liveupdate_start, liveupdate_update, or liveupdate_end.

The local start is reported once. Until then:

• A push whose timestamp is not newer than the local start is dropped (outdated_timestamp), and the local start stays unreported.
• A push without _xdm sends no tracking event, so the local start stays pending for a later push.
• A local start that is never reported is discarded after 28 days.