Builds the client state from the options: a new device from seed, or the
restored snapshot, plus the native transport client.
Invalid options throw what they always threw (a RangeError for the
request timeout, the native client's own error for a proxy or protocol mode
it rejects); a snapshot that cannot be restored throws
SnapshotDecodeError.
A restored snapshot keeps the application it carries, whatever build wrote
it: a session saved on 222 sends the 222 user agent, build number and the
rest of the snapshot's application, built with this release's request shapes
(owner, 2026-10-31, verbatim: «Что лежит в снапшоте, то и уходит. Сессия,
сохранённая на 222, шлёт User-Agent 222, номер сборки 222 и прочие данные
приложения из снапшота»). A version-bound field the snapshot omits is filled
from defaultApplication, because the request cannot be built without it —
the GraphQL doc-id table, GRAPHQL_OMIT_PRETTY, the Direct inbox
directInboxMode, the launch wire launchWire (the feed/timeline block,
the feeds' appnetsession pair, the shared launch requests, the inbox-tray
form, the save-credentials placement and the dictionary fan-out), the media
wires mediaLikeWire, mediaRepostWire and mediaNoteWire, the launch
constants shoppingExperiments and directSearchGenAiBotsLimit, the Bloks
prism palette, the Bloks theme bloksThemeParams, its INTERNAL_INFRA_THEME
spelling, the bk_client_context shape bloksClientContext, the zero-rating
table ZERO_HEADERS and the USDID registration's name
usdidRegistrationName. Nothing is replaced or dropped: every literal the
snapshot carries stays. A new process (no snapshot) runs defaultApplication
whole. See withDefaultVersionBoundFields.
The device and the session are the snapshot's own: the platform's
settleRestoredDevice hook fills the device facts a snapshot of the same
build may predate (settleAndroidDeviceFacts), so a restored device reports
what a fresh one of that build does.
The platform app layers and the tests build a process through it.
Builds the client state from the options: a new device from
seed, or the restoredsnapshot, plus the native transport client.Invalid options throw what they always threw (a
RangeErrorfor the request timeout, the native client's own error for a proxy or protocol mode it rejects); a snapshot that cannot be restored throws SnapshotDecodeError.A restored snapshot keeps the application it carries, whatever build wrote it: a session saved on 222 sends the 222 user agent, build number and the rest of the snapshot's application, built with this release's request shapes (owner, 2026-10-31, verbatim: «Что лежит в снапшоте, то и уходит. Сессия, сохранённая на 222, шлёт User-Agent 222, номер сборки 222 и прочие данные приложения из снапшота»). A version-bound field the snapshot omits is filled from
defaultApplication, because the request cannot be built without it — the GraphQL doc-id table,GRAPHQL_OMIT_PRETTY, the Direct inboxdirectInboxMode, the launch wirelaunchWire(thefeed/timelineblock, the feeds' appnetsession pair, the shared launch requests, the inbox-tray form, the save-credentials placement and the dictionary fan-out), the media wiresmediaLikeWire,mediaRepostWireandmediaNoteWire, the launch constantsshoppingExperimentsanddirectSearchGenAiBotsLimit, the Bloks prism palette, the Bloks themebloksThemeParams, itsINTERNAL_INFRA_THEMEspelling, thebk_client_contextshapebloksClientContext, the zero-rating tableZERO_HEADERSand the USDID registration's nameusdidRegistrationName. Nothing is replaced or dropped: every literal the snapshot carries stays. A new process (no snapshot) runsdefaultApplicationwhole. See withDefaultVersionBoundFields.The device and the session are the snapshot's own: the platform's
settleRestoredDevicehook fills the device facts a snapshot of the same build may predate (settleAndroidDeviceFacts), so a restored device reports what a fresh one of that build does.The platform app layers and the tests build a process through it.