The requests the Instagram iOS 425 app sends after a login that the 451
launch does not send. They are the 425 app's, not yet confirmed on 451:
the 451 launch is the restart 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 the 451 login's own post-login requests; 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 app
interleaves these requests with the launch-type requests, and in what order
the 451 app sends them after a login is not known. 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 app sends after a login that the 451 launch does not send. They are the 425 app's, not yet confirmed on 451: the 451 launch is the restart 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_statustail of the login, the IxT chain, the CXP notice). They wait for the 451 login's own post-login requests; 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 app interleaves these requests with the launch-type requests, and in what order the 451 app sends them after a login is not known. The 425 order among these requests is kept; they go one at a time, as in the 425 flow.