remoteConfig.getString doesn't return values for conditions based on user properties

[ttaranov]

[REQUIRED] Describe your environment

• Operating System version: MacOS
• Browser version: Latest Chrome 77
• Firebase SDK version: Latest/7.0
• Firebase Product: Remote Config

[REQUIRED] Describe the problem

Steps to reproduce:

Remote Config getString() (and I presume others), don't return correct values based on conditions setup using user properties

Relevant Code:

Maybe I'm doing something wrong, but here is what it is right now...

• setup remote config WelcomeMessage in firebase and define condition for a value based User Property state (say default value is Welcome! and for users with state=ca set value as Welcome CA!
• run code below and check output for remoteConfig.getString('WelcomeMessage') - no matter what I tried, the value always comes back as default and not based on the condition setup around user property

firebase.initializeApp(firebaseConfig);
const remoteConfig = firebase.remoteConfig();
remoteConfig.settings = {
    minimumFetchIntervalMillis: 3600000,
    defaultConfig: {
        'WelcomeMessage': 'Welcome Default'
    }
};

firebase.analytics().setUserProperties({
    state: 'ca'
},{
    global: true
});

remoteConfig.fetchAndActivate()
    .then(() => {
        console.log("Remote-config initialized")
        console.log(remoteConfig.getString('WelcomeMessage'))
    })
    .catch((err) => {
        console.error("Remote config error", err);
    });

[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.

[Feiyang1]

Thanks for reporting the issue! We found a problem with {global: true} that prevents user properties from being sent to our backend. We are working on a fix and will report back once it's fixed.

As a workaround for now, please set user properties without the global parameter:

firebase.analytics().setUserProperties({
    state: 'ca'
});

// send an event, so user properties are uploaded.
firebase.analytics().logEvent('eventName', {...});

Note: on web, user properties need to be uploaded for being used for targeting.

[ttaranov]

thank you for the response, although that didn't work either (I removed global, added logEvent). Is there no way to fetch remote configs with user attributes without involving analytics?

[Feiyang1]

Correct. User props need to be processed by analytics backend first, then they become available for targeting on Web. Remote config backend uses a device id to look up the corresponding user props at backend when you send a fetch request.

It's different than how it works in native SDKs where user props are attached to remote config fetch request at client side.

There might be a slight delay btw when you send the user props and when it becomes available for targeting. Have you tried after sometime?

Another way you can check is create an audience based on the user property. In the creation page, there should be a summary section that tells you how many users are in this audience. What number do you see?

[google-oss-bot]

Hey @ttaranov. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 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!

[google-oss-bot]

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

@ttaranov 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.