Unity 2022 Keeps Enabling Legacy Analytics

Hello!

The project in question does not use analytics, let alone legacy analytics. That means no analytics packages are installed.

The project was just upgraded from Unity 2021 to 2022 and the legacy analytics flag (m_Enabled) keeps getting enabled (see GitHub screenshot) whenever project settings are updated.

First time this happened I even received an e-mail from Unity saying they had detected legacy Unity analytics being enabled and that it’s now retired!

Am guessing this is a 2022 bug so just reporting.

9159179--1273988--UnityAnalyticsSetting.png

I’ve updated three different projects now (to 2022.LTS) and every single one of them is displaying this behaviour.

Both the Analytics & Legacy Analytics packages are uninstalled and\or disabled. Yet every time I open the project, the flag is set to 1 (i.e., enabled) and I have to undo the change in GitHub.

Is anyone else seeing this behaviour?

I just tried it, I don’t see the analytics getting enabled, no, it just keeps obsessively re-adding the urls for

m_EventOldUrl: https://api.uca.cloud.unity3d.com/v1/events
m_EventUrl: https://cdp.cloud.unity3d.com/v1/events
m_ConfigUrl: https://config.uca.cloud.unity3d.com
m_DashboardUrl: https://dashboard.unity3d.com

which is the same behaviour as 2021.

1 Like

Thanks for the info @AcidArrow

Tbh I just left those as is, assuming that if all the services were disabled they wouldn’t be used.

There used to be a bug where it would use those urls anyway, and bugs have a tendency of coming back.