Whether the running fiber is one of the process's background fibers or a child
of one: the hand-over (MobileProcessBackground.handOver) sets it on the work
it runs, and the process timers and the telemetry sender run in it. Two
readers: the set's own wait, so a fiber of the set never waits for the set to
empty, and the conformance harness, which judges a request of the process's
own background work on its own timeline (a walk's while a walk runs). The
declaration is published like every core export (the mobile barrel re-exports
it through mobile.process-background.js), and a platform package reaches it
by path. It belongs to whoever
runs a screen member now (provideCaptured carries it from the caller), so a
handle built in a tail's challenge answer and used by main does not carry it.
Whether the running fiber is one of the process's background fibers or a child of one: the hand-over (
MobileProcessBackground.handOver) sets it on the work it runs, and the process timers and the telemetry sender run in it. Two readers: the set's own wait, so a fiber of the set never waits for the set to empty, and the conformance harness, which judges a request of the process's own background work on its own timeline (a walk's while a walk runs). The declaration is published like every core export (the mobile barrel re-exports it throughmobile.process-background.js), and a platform package reaches it by path. It belongs to whoever runs a screen member now (provideCapturedcarries it from the caller), so a handle built in a tail's challenge answer and used bymaindoes not carry it.