![]() ![]() Show a loading indicator while fetching: In this case we show a loading indicator when the app starts up, load the remote config and then run the app once we have the updated remote config or the request failed.the benefit of this is that it happens in the background with no waiting time on the user. The main downfall of this is that the app UI might change while the user is using it. In the completion handler of the fetch you activate those values and then send a notification or something out to the UI to rebuild everything using the new values. Fetch, Activate and Update: You launch your application.There are three main ways of implementing a remote config flow. This simple functionality allows for us to have multiple ways of handling remote config updates as you'll see below. When you call apply fetched it then copies the new values over the remote config values making them available to read. Apply Fetched: After you call fetch values and they have been updated they sit in a separate location alongside your current config values.The firestore DB is a better fit for that if you want real-time solutions. You can use a duration 0 for making sure it fetches from the remote config immediately but that can cause throttling issues since this is not a real time solution. Which means if the user starts your app at 1pm and you change your remote values at 2pm they won't see it even if you restart the app and get it again. ![]() The default time for cache expiry is 12 hours. If you perform a fetch and the cache hasn't expired the cached values will be returned.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |