You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
--disable-analytics/--enable-analytics does not send an "analytics enabled/disabled" event via the unified_analytics package, yet one is sent via the deprecated usage package #160058
// The tool sends the analytics event *before* toggling the flag
// intentionally to be sure that opt-out events are sent correctly.
AnalyticsConfigEvent(enabled:true).send();
.
Notice we send an AnalyticsConfigEvent (via package:usage), but no corresponding package:unified_analytics event. package:usage is deprecated and the backend for it has long-since been sunset. I assume we should have always been sending the corresponding Event.analyticsCollectionEnabled from package:unified_analytics. Either that, or this event was only ever important for usage-to-unified-analytics migration, and is no longer important.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Fix analytics enabled/disabled event not being sent when the user ena…
github-actions commentedon Dec 26, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.