Remote config returns stale value

[Akash-Panigrahi]

Operating System

macOS 14.5

Browser Version

Chrome/123.0.6312.87

Firebase SDK Version

10.12.2

Firebase SDK Product:

Analytics, Remote-Config

Describe your project's tooling

Simple JS app with the parcel as the bundler

Describe the problem

Remote config fetchAndActivate returns previous results even when minimumFetchIntervalMillis is set to 0. I am trying to use a feature flag with a custom properties set.
This is being used in a web app.

Steps and code to reproduce issue

https://codesandbox.io/p/devbox/sparkling-https-nxwd7x?file=%2Fsrc%2Findex.mjs%3A35%2C1

The output is logged in the console. Using setUserProperties, I am accepting different values from remote-config.
I have set two simple conditions, that retrieve different segment_selection_variant based on ProfileID.

[google-oss-bot]

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

[jbalidiong]

Hi @Akash-Panigrahi, apologies for the delay. I'm wasn't able to reproduce the behavior that you've mentioned. Let me know if I may have misunderstood anything, I tried following your code implementation and running the app. Here's what I did on my end:

1. Load the app with parceljs
2. The initial remote config value is B.

3. Change remote config value to A.

Checking the logs, it reflects the actual values upon changing in the console. You've mentioned the stale value of the remote config, are you seeing this upon changing in the console and refreshing the app? Can you also provide the steps on how to replicate the issue including the remote config value in the console.

[Akash-Panigrahi]

@jbalidiong Hey, thanks for checking this out.

The yellow marked boxes make up the first request and the blue ones form another.

• The expectedOutput and actualOutput for the yellow one is B.
• For the blue, the expectedOutput is A while the actualOutput is B, which is wrong.
  • This is picking the cached value from the first request.