When actionType is undefined (e.g. a malformed or unexpected event cast from unknown), the breadcrumb message says Dispatched NAVIGATE and implies a NAVIGATE action, but since action_type is omitted from data in that case, the message is inconsistent and could mislead debugging. Consider using 'UNKNOWN' as the fallback instead.

The test calls mockNavigation.finishAppStartNavigation(), which only fires listeners['state'] — it never triggers listeners['__unsafe_action__']. Since the dispatch breadcrumb lives in startIdleNavigationSpan (bound to __unsafe_action__), the test never invokes that function at all and passes trivially, leaving the actual isAppRestart = true guard untested.

When actionType is undefined, the message says Dispatched NAVIGATE but the data object omits action_type, so the message contradicts the structured data and misattributes the dispatch type.

The new test 'does not create dispatch breadcrumb for app restart' (reactnavigation.test.ts:1800–1826) calls mockNavigation.finishAppStartNavigation(), which only fires the state listener and never the __unsafe_action__ listener. Since the navigation.dispatch breadcrumb is emitted exclusively inside startIdleNavigationSpan (reactnavigation.ts:353) — which is wired to the __unsafe_action__ listener — the breadcrumb code path is never reached in this test. The assertion expect(dispatchCall).toBeUndefined() therefore passes regardless of whether the !isAppRestart guard exists, so the real app-restart suppression path (invoked via getAppRegistryIntegration → onRunApplication → startIdleNavigationSpan(undefined, true)) remains unverified.