The Pigeon channel as a platform declares it (MobileTelemetryChannels):
due when the earliest pending event's own deadline comes, once the process
began its Pigeon session; sent at the app's start, its going to the
background and coming back, its close and the caller's explicit flush. The
platform closes it over the process's services. Outside the session it
sends nothing at a lifecycle moment, and the explicit flush refuses
(TelemetryDeliverySessionError). Its app-start upload is where the logger
opens its store, so the process start's counters are counted there
(countPigeonProcessStart): a process restored from a checkpoint has no
start of its own and counts none.
Published because @igpapi/mobile/telemetry/telemetry.channels.js — a
published subpath — re-exports it: a symbol another published package's
declaration names is part of this package's published surface
(repository-topology-obfuscation-and-published-declarations.md).
The Pigeon channel as a platform declares it (
MobileTelemetryChannels): due when the earliest pending event's own deadline comes, once the process began its Pigeon session; sent at the app's start, its going to the background and coming back, its close and the caller's explicit flush. The platform closes it over the process's services. Outside the session it sends nothing at a lifecycle moment, and the explicit flush refuses (TelemetryDeliverySessionError). Its app-start upload is where the logger opens its store, so the process start's counters are counted there (countPigeonProcessStart): a process restored from a checkpoint has no start of its own and counts none.Published because
@igpapi/mobile/telemetry/telemetry.channels.js— a published subpath — re-exports it: a symbol another published package's declaration names is part of this package's published surface (repository-topology-obfuscation-and-published-declarations.md).