'Android Firebase Remote Config initial fetch does not return value

I'm using Firebase Remote Config to fetch data when app first open for the first time. But problem is I cannot fetch data on first start of the app. onComplete() method triggers but returns no value. If I close app and run again it returns value from Remote Config.

Tried to call fetch() in onCreate(), onStart(), onResume(), gave it a second delay with postDelay() still the same, initial fetch is always empty. I know, Remote Config has setDefaults() method to store defaults before it is getting fetched, but setting defaults inside app is not what I want.

It is the way how Remote Config works or am I doing something wrong? The only workaround I found is to add fetch() inside onResume() and call onResume() again inside onCreate(). It results calling onResume() twice. First time by Android system and second time by code.

It there any other way to force Remote Config fetch data on first time run?

UPDATE

Inside onComplete() first I must call firebaseRemoteConfig.activateFetched(); before getting new values from it.

Solution 1:^[1]

mFirebaseRemoteConfig = FirebaseRemoteConfig.getInstance();
        FirebaseRemoteConfigSettings configSettings = new FirebaseRemoteConfigSettings.Builder().build();
        mFirebaseRemoteConfig.setConfigSettingsAsync(configSettings)
                .addOnCompleteListener(task -> mFirebaseRemoteConfig.fetchAndActivate()
                        .addOnCompleteListener(activity, task1 {
                       // now cache is updated you can fetch values
                       String value = mFirebaseRemoteConfig.getString("key");
               }));

Start getting the values after config settings are completed

just do that at the app launch, and get values directly anywhere else (eg: mFirebaseRemoteConfig.getString("key");)

Solution 2:^[2]

check few points:

Once new variable is created in firebase dashboard, publish it

fetch with cache time set to 0

FirebaseRemoteConfig.getInstance().fetch(0).

Solution 3:^[3]

I understand that this is an old question - but I ran into exactly the same issue as the asker. After investigating this for a few days I was able to find an answer so I will post it here to help anyone else who is having difficulties.

The first thing to check is that your config settings are published in Firebase. After making a change there is a Publish button on the top right of the console.

I had followed numerous tutorials and guides onto how configure FireBases Remote Config in Unity but despite calling ActivateFetched I got no results. After investing a great deal of effort trying to figure out why no data was being returned I stumbled across this thread: https://github.com/firebase/quickstart-unity/issues/9

It turns out RemoteConfig doesn't work in Unity and will only use the defaults. To actually using your remote config you must do a build and deploy it onto your target device.

On my Android device all of my remote config is retrieved successfully

Solution 4:^[4]

Thanks to Pankaj kumar answer, I set firebase.remoteConfig().settings.minimumFetchIntervalMillis = 0 and worked

Solution 5:^[5]

Simply just try to reset your config locally before getting it to prevent wrong values from getting back.

 val firebaseRemoteConfig = Firebase.remoteConfig

 firebaseRemoteConfig.reset()

 firebaseRemoteConfig.fetch(0)
    .addOnCompleteListener { taskFetch ->
        if (taskFetch.isSuccessful) {
            firebaseRemoteConfig.activate().addOnCompleteListener { task ->
                if (task.isSuccessful) {
                 //do what you want..
                }
            }
        }
    }

Just the point is firebaseRemoteConfig.reset() before the activation is called.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1
Solution 2	Pankaj kumar
Solution 3	user1662292
Solution 4	wisetap.dev
Solution 5	TinaTT2

'Android Firebase Remote Config initial fetch does not return value

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]