Menu
When I update my app version, will the firebase remote config cache resets and fetches new values or uses the existing cache, until the cache expires on set time
998
The caching of configuration values is explained in the documentation. Because of the throttling limits, it is not possible for your released app to immediately see changes in Remote Config values. Cached values will be used until the next fetch is allowed. The default cache expiration is 12 hours.
Remote Config includes a client library that handles important tasks like fetching parameter values and caching them, while still giving you control over when new values are activated so that they affect your app's user experience. This lets you safeguard your app experience by controlling the timing of any changes.
In the Firebase console, open your project. Select Remote Config from the menu to view the Remote Config dashboard.
Download and then add the Firebase Android configuration file ( google-services.json ) to your app: Click Download google-services.json to obtain your Firebase Android config file. Move your config file into the module (app-level) root directory of your app.
It won't.
It fetches new values after the cache timeout and the cache stays even after an App update.
Though, you can call fetch(Long) with a timeout in seconds that is significant smaller than the default value but according to the Google Blog, this might be risky.
A smaller timeout might be used if you write some code that decides that this is the first app start after an update, but while you can reduce this cache time somewhat, if you start making network calls too frequently, your app might start getting throttled, either by the client, or the Remote Config service. (from the blog post linked above)
169
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
