Without the real-time Remote Config API in the JS/Web SDK, user properties become useless as conditions for parameters. In our app, many of our parameters are conditional on the user's organization ID. So after the user logs in, we call `setUserProperties` to set the organization ID that they are a member of. But because we do not have access to the real-time API like iOS and Android do, our app can't update the Remote Config parameters to what they should be with the organization ID. It doesn't even matter if we set `minimumFetchIntervalMillis` to 0. No matter how many times we call `fetchAndActivate` after calling `setUserProperties`, the config never updates to the correct values. The only way we can get it to update is by refreshing the web page a couple times, and we have no idea why that works but calling `fetchAndActivate` doesn't.
Without the real-time Remote Config API in the JS/Web SDK, user properties become useless as conditions for parameters. In our app, many of our parameters are conditional on the user's organization ID. So after the user logs in, we call `setUserProperties` to set the organization ID that they are a member of. But because we do not have access to the real-time API like iOS and Android do, our app can't update the Remote Config parameters to what they should be with the organization ID. It doesn't even matter if we set `minimumFetchIntervalMillis` to 0. No matter how many times we call `fetchAndActivate` after calling `setUserProperties`, the config never updates to the correct values. The only way we can get it to update is by refreshing the web page a couple times, and we have no idea why that works but calling `fetchAndActivate` doesn't.