The process's tray session: the id the app mints once when the process
starts and then sends on every request of the stories tray and names in its
own telemetry. It is one process fact, like MobileNavigation: one per
runtime layer, never in the session snapshot, and a new process starts with
a new one. A checkpointed process keeps it — the restore puts the id back —
because a restore continues the same process.
The Android 451 recording shows it as the one owner of both spellings:
feed/reels_tray sends it as tray_session_id
and every ig_profile_action of the recording carries the same value
without its dashes as story_ranking_token. So a profile visit's ranking
token is this id, not an identity of the visit.
The process's tray session: the id the app mints once when the process starts and then sends on every request of the stories tray and names in its own telemetry. It is one process fact, like
MobileNavigation: one per runtime layer, never in the session snapshot, and a new process starts with a new one. A checkpointed process keeps it — the restore puts the id back — because a restore continues the same process.The Android 451 recording shows it as the one owner of both spellings:
feed/reels_traysends it astray_session_idand everyig_profile_actionof the recording carries the same value without its dashes asstory_ranking_token. So a profile visit's ranking token is this id, not an identity of the visit.