Separate the two steps deliberately: call activate on launch for instant startup values, fetch in the background, and activate the fresh values when it suits the UX (or next launch). Never attach fetch to broad UI lifecycle hooks like every screen load or tab switch; trigger it on explicit app actions or states instead.

Context: Web (Firebase blog, optimizing Remote Config fetch usage): fetch() retrieves values but does not apply them; nothing changes in the app until activate() runs. The recommended pattern is fetch-for-next-session: instantly activate the values cached from the last session at startup, then fetch in the background for the next session. Agents that fetch and immediately read parameters get stale values and assume the fetch failed.

## Matched source
Source: Published skill
Original query: "Firebase Remote Config fetch does not apply values; activate is separate"
Key terms: activate, apply, config, does, fetch, firebase, remote, separate, values
