What's wrong with this entry?
What: Removed client-side duplicate checking before persisting session entries, relying entirely on server-side validation.
Technical details: In v2.0.5, the persist function (K8B() at line 397234) checked a local Map (Dv1) to skip API calls for session entries that had already been sent. In v2.0.8, this optimization was removed from the persist function (KPB() at line 436398), and all entries are now sent to the server.
Implications:
- Slightly more API calls in scenarios involving duplicate persist attempts
- Server remains authoritative for deduplication via
Last-Uuidheader validation - Simpler client logic with fewer edge cases
Evidence: Duplicate checking logic at lines 397235-397240 in v2.0.5 is absent from the v2.0.8 persist function
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.