User property from future set on View Loads about dd-sdk-android HOT 8 CLOSED

Thanks for details! The problem is clear and we will try to address it.

from dd-sdk-android.

The fix is a part of the 2.6.0 release.

from dd-sdk-android.

Hello @geranzo!

Can you please share the way you set these user properties?

Is it done like that:

val propertiesA = mapOf("a" to "b")
GlobalRumMonitor.get().addAction(..., propertiesA)
val propertiesB = mapOf("c" to "d")
GlobalRumMonitor.get().startView(..., propertiesB)

or you are utilizing Datadog.setUserInfo to set them?

Basically code snippets will be useful to understand the setup you have. By looking on the description, it seems that you also start/stop views manually, not using our built-in tracking strategies?

from dd-sdk-android.

Can you please share the way you set these user properties?

This is our method to set a user property:

    override fun setUserProperty(name: String, value: Any?) {
        if (value != null) {
            globalRum.get().addAttribute(name, value)
        } else {
            removeUserProperty(name)
        }
    }

Basically code snippets will be useful to understand the setup you have. By looking on the description, it seems that you also start/stop views manually, not using our built-in tracking strategies?

Yes, we call globalRum.get().startView(...) ourselves on a callback from Compose Navigation library.

from dd-sdk-android.

Thanks for a quick response. Can you please expand removeUserProperty method? Does it call globalRum.get().removeAttribute? And at which point do you call setUserProperty - is it only navigation events?

Also is it possible that calls to send custom action are coming from non-UI thread (shouldn't be an issue, but just for the understanding)?

Yes, we call globalRum.get().startView(...) ourselves on a callback from Compose Navigation library.

We have dd-sdk-android-compose module with NavigationViewTrackingEffect to auto-instrument Compose Navigation. If it doesn't work for your setup, we are open to improve it per your feedback.

from dd-sdk-android.

Can you please expand removeUserProperty method? Does it call globalRum.get().removeAttribute?

Yes, it does:

    override fun removeUserProperty(name: String) {
        globalRum.get().removeAttribute(name)
    }

And at which point do you call setUserProperty - is it only navigation events?

No, we have a couple more properties that we want to track for the user like e.g. state of a ringer mode or DnD state, theme light or dark etc.

Also is it possible that calls to send custom action are coming from non-UI thread (shouldn't be an issue, but just for the understanding)?

No, every time we are about to call some API like addAttribute, startView or addAction etc., we launch a coroutine on Dispatchers.Main.immediate.

We have dd-sdk-android-compose module with NavigationViewTrackingEffect to auto-instrument Compose Navigation. If it doesn't work for your setup, we are open to improve it per your feedback.

It wasn't probably available at the time we were integrating with DD.

from dd-sdk-android.

Closing this as it was fixed and will be delivered in the our next sdk release.

from dd-sdk-android.

Thank you! Very much appreciated.

from dd-sdk-android.