Remote Config not pulling latest configuration without hard cache reload on web about firebase-js-sdk HOT 6 CLOSED

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

from firebase-js-sdk.

Hi @enterprisecoderr, thanks for reaching out to us. I'm wasn't able to reproduce the behavior that you've mentioned. I tried fetchAndActivate() using the ff:

1. Edit the src/app/app.tsx to be:

const remoteConfig = getRemoteConfig(app);

remoteConfig.settings.minimumFetchIntervalMillis = 0;
fetchAndActivate(remoteConfig)
.then(()=>{
  const value = getValue(remoteConfig, "someKey")
  .asString()
  console.log(`Value: ${value}`);

})

2. Run npm run start
3. Visit the http://localhost:4200/
4. Update the remote config value in the console
5. Refresh the page and get the updated value.

To get a better understanding of what’s causing the failed fetch, could you provide a minimal, but complete sample of a project that I can run locally.

from firebase-js-sdk.

I am not using the bundled fetchAndActivate command. I'm calling activate and then later fetchConfig. Can you try with that setup?

from firebase-js-sdk.

Hi @enterprisecoderr, I tried using the fetchConfig and activate but I still wasn't able to replicate the behavior. Here is the sample snippet of my code:

fetchConfig(remoteConfig)
.then(()=>{
  activate(remoteConfig)
.then(()=>{
    const value = getValue(remoteConfig, "someKey")
    .asString()
    console.log(`Value: ${value}`);
  
  })
.catch((error)=>{
    console.log(error)
  });
})
.catch((error)=>{
  console.log(error)
});

I used .then() and called activate() to avoid any race condition as both activate and fetchConfig returns a promise. Could you try following the implementation and see if the behavior persists.

from firebase-js-sdk.

Hey @enterprisecoderr. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

from firebase-js-sdk.

Since there haven't been any recent updates here, I am going to close this issue.

@enterprisecoderr if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

from firebase-js-sdk.