DirectInboxFragment:direct_inbox, the Direct tab (Android 451). The tab
refresh (direct_v2/inbox/) is sent while the previous screen is still in
front, then the tab comes to front. The inbox's own extras are not sent: the
app's pending-inbox and presence queries are GraphQL calls whose shapes the
library has no builder for (the REST bricks send another wire), the app's
quick_reply/get form is signed differently from the brick's, and
feed/get_latest_reel_media needs tray participants the library does not
keep.
mode is a fact of the presented profile, read by directInboxFeed itself:
the 451 profile sends mode=2, the 448 profile sends none.
The answer's seq_id is kept, and it is required: the app's "New message"
flow reports it as the participant lookup's seq_id (the group-creation
recording's lookup sends the inbox answer's sequence), and openNewMessage
hands it to the picker. A snapshot without one is not an inbox answer and
fails the data check; no fallback number stands in for it.
DirectInboxFragment:direct_inbox, the Direct tab (Android 451). The tab refresh (direct_v2/inbox/) is sent while the previous screen is still in front, then the tab comes to front. The inbox's own extras are not sent: the app's pending-inbox and presence queries are GraphQL calls whose shapes the library has no builder for (the REST bricks send another wire), the app'squick_reply/getform is signed differently from the brick's, andfeed/get_latest_reel_medianeeds tray participants the library does not keep.modeis a fact of the presented profile, read bydirectInboxFeeditself: the 451 profile sendsmode=2, the 448 profile sends none.The answer's
seq_idis kept, and it is required: the app's "New message" flow reports it as the participant lookup'sseq_id(the group-creation recording's lookup sends the inbox answer's sequence), andopenNewMessagehands it to the picker. A snapshot without one is not an inbox answer and fails the data check; no fallback number stands in for it.