Firebase-ios-sdk: RemoteConfig bug with user property

[theo68hh]

Xcode version: 11.1 GM Seed
Firebase SDK version: 6.9.0
Firebase Component: [RemoteConfig]

Describe the problem

The conditions in Remote Config do not seems to work for the users properties that we create ourselves.

Example: I put the email condition contains "[email protected]" and despite that I send in the user properties "[email protected]" the conditions do not work and it takes the default value.

To initialize the email property I use the following code
Analytics.setUserProperty(connectedUser.lastKnownInfo.email, forName: UserProperties.Email) 
When I look at the debugView we also see that the property is sent to Firebase.

After creating user property, when fetching and retrieving information from RemoteConfig with :
RemoteConfig.remoteConfig().fetchAndActivate and RemoteConfig.remoteConfig().configValue(forKey: key.rawValue).stringValue

The retrieved information are not the same as the configured condition for the instantiated user property.
The condition in Remote Config is

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[Bexcode-iOS]

@dmandar When can we expect this to be completed?

[wojteklu]

Same issue happens for me in version 6.14.0.

[wojteklu]

@dmandar @paulb777 Do you need steps or sample code for the issue? It's critical error that prevents to update the library.

[rizafran]

Hi @wojteklu, yes, providing steps or sample code would help us to easily replicate the issue.

[wojteklu]

@theo68hh @dmandar @rizafran In my case, I was using Carthage builds and the problem was missing FIRAnalyticsConnector in Link binary with libraries. Since after carthage update, you have to add new libraries by hand in Xcode. It is not validated by FirebaseAnalytics if FIRAnalyticsConnector is added to target so it was hard to find the issue.

[paulb777]

Thanks for the update @wojteklu.

We'll think about ways to make it less tricky to find issues like this. It's a bit tricky since it is intentional for Analytics usage to be optional with Firebase.