The requests the Instagram iOS 425 post-login recording carried that
neither 451 recording shows. Verified on 425, not re-captured on 451:
both 451 recordings (appstart1, run 8) are restarts of an app that already
holds a session, not the first start after a login, and many of these read as
once-after-login work (the full config sync, the ML-model downloads, the
content-filter dictionaries, the caa.notif_status tail of the login, the IxT
chain, the CXP notice). They wait for a clean 451 recording of a login; until
then they keep their 425 shapes, their 425 GraphQL form and their 425 doc ids
(so they do not present as 451 on the wire).
After a login run this flow, then IosAppLaunchFlow: the 425 recording
interleaved these requests with the launch-type requests, and in what order
the 451 app sends them after a login is not recorded. The 425 order among
these requests is kept; they go one at a time, as in the 425 flow.
The requests the Instagram iOS 425 post-login recording carried that neither 451 recording shows. Verified on 425, not re-captured on 451: both 451 recordings (
appstart1, run 8) are restarts of an app that already holds a session, not the first start after a login, and many of these read as once-after-login work (the full config sync, the ML-model downloads, the content-filter dictionaries, thecaa.notif_statustail of the login, the IxT chain, the CXP notice). They wait for a clean 451 recording of a login; until then they keep their 425 shapes, their 425 GraphQL form and their 425 doc ids (so they do not present as 451 on the wire).After a login run this flow, then
IosAppLaunchFlow: the 425 recording interleaved these requests with the launch-type requests, and in what order the 451 app sends them after a login is not recorded. The 425 order among these requests is kept; they go one at a time, as in the 425 flow.