Data not populated anymore after Sep/6 commit

[mauriciolima1988]

Hi folks, I work for a big client as Android engineer, we use Kochava through MParticle kit, we're currently using the following repos:

com.mparticle:android-appboy-kit:5.50.0
com.mparticle:android-core:5.50.0
com.mparticle:android-kochava-kit:5.50.0

So we never done Kochava initialization actually, it looks that everything is happening under the hood through MParticle, we only do MParticle.start and MParticle.login.

After out release cut on Sep/13 got ramped to 100% users, marketers noticed that app_userid is no longer populated in Kochava data, we can see a 90% drop in number from one day to the next day. We haven't done any changes that could potentially lead to this, but looking at your repo I found this commit changing some stuff related to identityLinks and user id.

They figured that out by doing the following SQL query in the Kochava dashboard

SELECT DATE(i.date_received), COUNT(DISTINCT id.identity_value)
FROM installs_primary as i
JOIN identity_link as id
ON i.kochava_device_id = id.kochava_device_id
WHERE date(i.date_received) >= '2023-09-01'
GROUP BY 1
ORDER BY 1 DESC

The results showed 90% drop in number the exact same day our release cut was ramped to 100% of users, and our release was cut 6 days after that commit , so I have a few questions:

1. What we can do now on Android side to have that data populated again? Just update from 5.50.0 -> 5.55.0 will do it?
2. I tried adding the following code before MParticle.start() like the documentation says (just for testing)

val identityLink: MutableMap<String, String> = mutableMapOf()
identityLink["app_userid"] = "my_test_user_id"
KochavaKit.setIdentityLink(identityLink)

then I could find this "my_test_user_id" on Kochava SQL identity_link(table)->identity_value(column), but I still can't figure out how to make that data (the comparison from the SQL query) to get populated again as it was before.

Any help here would be appreciated, we have no backend set for Kochava so everything is on mobile side.

[Mansi-mParticle]

@mauriciolima1988 Thank you for bringing this to our attention, and sincere apologies for the long delay in addressing this issue.
We’ve now created an internal Jira ticket to investigate and resolve this problem. Our team will review it and we’ll get back to you with updates as soon as possible. Ticket