What's wrong with this entry?
A new clientData fetching system that pulls configuration and feature data from the server at session start, with caching, retry logic, and 401 token refresh.
Feature-flagged — appears to require OAuth subscriber status with specific profile scopes.
- Fetches client data on session start with exponential backoff retries
- Caches responses to disk; skips writes if unchanged
- Handles 401 by refreshing OAuth tokens and retrying
- Skipped when "nonessential traffic" is disabled or when user lacks the required OAuth scopes
Client data infrastructure (search for "[clientData] fetch ok")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.