partner_started_game / partner_completed_part now route to the specific game route (gameRouteForType(payload.gameType)) so the game screen auto-joins the couple's active session — fulfilling the 'Tap to join!' promise. Server already sends game_type in the FCM data; client now parses it (AppMessagingService + MainActivity) into PartnerNotificationPayload and routeFor maps it. game_results_ready stays on the hub pending a server change to also send game_session_id (completed sessions aren't returned by getActiveSession, so the plain game route would show setup). Verified live: backgrounded partner tapped the start-game push -> opened This or That at 1/5 (joined), not the hub. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| schemas | ||
| src | ||
| build.gradle.kts | ||
| proguard-rules.pro | ||