When your app fetches parameter values from the Remote Config service, those values are cached locally but not activated. To activate fetched values so that they can TAKE effect, call activateFetched. This design lets you control when the behavior and appearance of your app changes, because you can choose when to call activateFetched. After you call activateFetched, your app source CODE determines when UPDATED parameter values are used.

For example, you could fetch values and then activate them the next time a user starts your app, which REMOVES the need to delay app startup while your app waits for fetched values from the service. Changes to your app's behavior and appearance then occur when your app USES the updated parameter values.

When your app fetches parameter values from the Remote Config service, those values are cached locally but not activated. To activate fetched values so that they can take effect, call activateFetched. This design lets you control when the behavior and appearance of your app changes, because you can choose when to call activateFetched. After you call activateFetched, your app source code determines when updated parameter values are used.

For example, you could fetch values and then activate them the next time a user starts your app, which removes the need to delay app startup while your app waits for fetched values from the service. Changes to your app's behavior and appearance then occur when your app uses the updated parameter values.