Update README.md

[Bentlybro]

[akshaynarisetti]

Much clearer now, thanks!

[ellaaicare]

iOS Investigation - Root Cause Analysis

After investigating the iOS codebase and backend integration:

iOS Side (Not the issue)

• getConversations() in lib/backend/http/api/conversations.dart does NOT filter by source
• Queries /v1/conversations?include_discarded=true&limit=50&offset=0&statuses=processing,completed
• Uses ServerConversation.fromJson() which should handle any valid conversation

Backend Side (Likely issue)

The V2 pipeline stores conversations via FirestoreClient.store_voice_conversation() which writes directly to Firestore:

# Path: users/{uid}/conversations/{session_id}
conversation_data = {
    'id': session_id,
    'uid': uid,
    'created_at': datetime.utcnow(),  # ⚠️ Using naive datetime
    'transcript': transcript,
    'transcript_segments': segments,
    'source': source,
    'status': 'completed',
    'discarded': False,
    'is_voice_conversation': True,
    'turn_count': len(segments),
}

Potential Issues Found:

1. Timezone-naive datetimes: V2 uses datetime.utcnow() which creates timezone-naive datetimes. The get_conversations() query may fail with created_at comparisons. Should use datetime.now(timezone.utc).

2. Missing required fields: The normal conversation flow uses upsert_conversation() which includes many more fields:

   • language
   • structured (with title, overview, emoji, category, etc.)
   • started_at / finished_at
   • plugins_results
   • geolocation

3. No encryption: Normal conversations use _prepare_conversation_for_write() which handles encryption. V2 bypasses this.

4. Firestore composite index: The query uses (discarded, status, created_at DESC) - if V2 conversations have incompatible field types, they may be silently excluded.

Recommended Backend Fix:

V2 should use the same upsert_conversation() function from database/conversations.py instead of direct Firestore writes. This ensures consistent field structure, encryption, and indexing.

Quick Test:

Check if the V2 conversations appear with this query (bypasses REST API):

# In Firebase console, query:
# users/{uid}/conversations where source == 'voice_mode_v2_manual'

If they exist there but not via API, it's a query/field mismatch issue.

This is a backend issue, not iOS.