App: Missing reportActions! 😱

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

HOLD on https://github.com/Expensify/App/pull/13118

Action Performed:

On dev, do yourself a favor and change the pagination size from 50 to 5 here. The bug is still valid with a larger page size, just easier to reproduce with a smaller one.

+ $indexedHistory = ReportAPI::getIndexedHistory($authToken, $reportID, -1, '', 5, Report::ACTION_ORDER_DESC, $shouldKeyReportActionsByID);
- $indexedHistory = ReportAPI::getIndexedHistory($authToken, $reportID, -1, '', Report::ACTIONS_PAGINATION_LIMIT, Report::ACTION_ORDER_DESC, $shouldKeyReportActionsByID);

Sign in on two separate accounts, A and B.
On account A, send 5 messages to account B: 1, 2, 3, 4, 5
As user A, go offline but keep the app open.
As user B, send 15 responses – 6 through 20
As user A, come back online.

Expected Result:

User A should see chats 1-20, without any missing, OR a more robust solution that depends on bidirectional pagination would be to:
We display a skeleton UI between chats 6 and 16 to signify a gap where reportActions are missing. In production w/ our page size of 50, you probably would never see both sides of the “gap” on the screen at the same time. Scrolling into the the gap from above or below should trigger an API request to fill in the missing reportActions (or at least, one page of missing reportActions).