Closed mulundapm closed 4 months ago
As far as I understand, the age_group is taken from the users table and tvos is not logging that event. npaw probably doesn't have a property for the age. Theory: tvos never logged the necessary but was able to gather the age since the mobile app did log it. But the user_id on tvos now looks different so that that accidental hack stopped working.
As far as I understand, the age_group is taken from the users table and tvos is not logging that event. npaw probably doesn't have a property for the age. Theory: tvos never logged the necessary but was able to gather the age since the mobile app did log it. But the user_id on tvos now looks different so that that accidental hack stopped working.
huh, the userid shouldnt look different. what do you mean? - how different?
I remember seeing that we are sending age group to NPAW sometimes, but not always.
Using REPLACE(s.user_id, " ", "+")
fixes the change that happened in February when we updated the npaw version.
However, it doesn't fix that for users that don't use mobile, we don't have age information.
Using
REPLACE(s.user_id, " ", "+")
fixes the change that happened in February when we updated the npaw version. However, it doesn't fix that for users that don't use mobile, we don't have age information.
oh noo. npaw needs to fix this
age is sometimes empty for data coming from bccm-tvos.
I forgot that we have public users on tvOS... My fix in 4.2.9 is working. Look at this from npaw_playback_sessions filtered on 4.2.9:
but there are two weird things here.
Npaw needs to fix their encoding issues so that "+" doesnt become " ".
We can make a new issue for next sprint to follow up, 0 points.
New issue: #12
age is sometimes empty for data coming from bccm-tvos.
deployment is not part of the story point, do not spend more than 2 story points on this!!!