User Property values coming in late

[toainguyenvan20102002]

[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source

Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2021.3.25
• Firebase Unity SDK version: 9.0.0
• Source you installed the SDK: .unitypackage (.unitypackage or Unity Package Manager)
• Problematic Firebase Component: Analytics (Auth, Database, etc.)
• Other Firebase Components in use:Cloud Messaging, Crashlytics, Remote Config (Auth, Database, etc.)
• Additional SDKs you are using: Max Mediation (Facebook, AdMob, etc.)
• Platform you are using the Unity editor on: Windows (Mac, Windows, or Linux)
• Platform you are targeting: Android, iOS (iOS, Android, and/or desktop)
• Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:

(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)

Steps to reproduce:

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.

If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.

Relevant Code:

// TODO(you): code here to reproduce the problem

We have been using a few user properties (or custom definitions) in our project since it was launched a couple of years ago. We noticed that throughout reports our user properties appear to come in a little late, and are not updated frequently.

In the image below, for example, you can see the events coming in through a Debug View. The orange clean user property gets set at 11:10:00AM, however it should have been before the earn_virtual_currency events fired at 11:09:58AM as per our code. It appears that, for some reason, the user property has a delay that the analytics do not share when being set?