Read the rest of the WhatsApp call record on iOS - #2163
Merged
Conversation
CallHistory.sqlite keeps an aggregate row beside each call, and the call row itself carries more than the artifact was reading. Adds whether the call was video, the app's own incoming flag, whether it was missed and the missed reason, the bytes sent and received, the call id, the group jid and the aggregate id the row belongs to. The aggregate is per group of calls rather than per call, so the notes say which columns describe the group. The stored incoming flag agrees with the direction the artifact already derived on every row where both are present, and it fills in on the one tested image whose release has no group call creator column and so has no derived direction. Columns absent from older databases are resolved to NULL the same way the existing group call creator column already is. Every column the artifact produced before is unchanged on all eight tested images. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The two committed whatsAppCallHistory snapshots still carry the eight column headers from before the call-detail columns were added, so the test-case gate fails on the header list. Re-recorded from the same committed fixtures with the current code. josh_ios15_ffs stays at 4 rows and mvs_ios_2023 at 0, and every value in the eight pre-existing columns is unchanged, matched row by row on those columns. The nine new columns carry the stored call detail. The whatsApp module now reports PASS on all five units, and the full run is PASS=154, KNOWN_FAIL=1, FAIL=0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CallHistory.sqlite keeps an aggregate row beside each call, and the call row itself carries more than the artifact was reading. Adds to WhatsApp - Call History:
The aggregate is per group of calls rather than per call and the notes say so. The stored incoming flag agrees with the direction the artifact already derived on every row where both are present, and it fills in on the one tested image whose release has no group call creator column. Columns absent from older databases resolve to NULL the same way the existing creator column does, and every column the artifact produced before is unchanged on all eight tested images.
🤖 Generated with Claude Code