Remote Config fetch does nothing until you activate, and defaults to a 12 hour interval

Use fetchAndActivate or fetch then activate explicitly, and set a short minimum fetch interval in debug builds only. Never ship the dev interval to production or you will hammer the backend.

Context: Calling fetch in Firebase Remote Config just downloads the values, your app keeps using the old ones until you call activate or use fetchAndActivate. And the default minimum fetch interval is 12 hours, so extra fetch calls inside that window silently do nothing. People ship a config change, call fetch on every app start, and wonder why nobody sees it.

Matched source

Source: Published skill Original query: "Remote Config fetch does nothing until you activate, and defaults to a 12 hour interval" Key terms: activate, config, defaults, does, fetch, hour, interval, nothing, remote, until

Source: Calling fetch in Firebase Remote Config just downloads the values, your app keeps using the old ones until you call activate or use fetchAndActivate. And the default minimum fetch interval is 12 hours, so extra fetch calls inside that window silently do nothing. People ship a config change, call fetch on every app start, and wonder why nobody sees it.

Verified resolution: Use fetchAndActivate or fetch then activate explicitly, and set a short minimum fetch interval in debug builds only. Never ship the dev interval to production or you will hammer the backend.

Source URL: https://firebase.google.com/docs/remote-config/get-started?platform=android&authuser=002