The macOS build in the previous commit flipped UnityConnectSettings.m_Enabled from 0 to 1 as a side effect of running through the authenticated CLI. Nothing asked for that, and it was off before. The sub-settings — Insights, crash reporting — were already 0 and stayed 0, so nothing was actually being sent. It may well flip again on the next build. If it does, that is why. Co-Authored-By: Claude Opus 5 <[email protected]>
41 lines
1.0 KiB
Plaintext
41 lines
1.0 KiB
Plaintext
%YAML 1.1
|
|
%TAG !u! tag:unity3d.com,2011:
|
|
--- !u!310 &1
|
|
UnityConnectSettings:
|
|
m_ObjectHideFlags: 0
|
|
serializedVersion: 1
|
|
m_Enabled: 0
|
|
m_TestMode: 0
|
|
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
|
|
m_TestInitMode: 0
|
|
InsightsSettings:
|
|
m_EngineDiagnosticsEnabled: 1
|
|
m_Enabled: 0
|
|
CrashReportingSettings:
|
|
serializedVersion: 2
|
|
m_EventUrl: https://perf-events.cloud.unity3d.com
|
|
m_EnableCloudDiagnosticsReporting: 0
|
|
m_LogBufferSize: 10
|
|
m_CaptureEditorExceptions: 1
|
|
UnityPurchasingSettings:
|
|
m_Enabled: 0
|
|
m_TestMode: 0
|
|
UnityAnalyticsSettings:
|
|
m_Enabled: 0
|
|
m_TestMode: 0
|
|
m_InitializeOnStartup: 1
|
|
m_PackageRequiringCoreStatsPresent: 0
|
|
UnityAdsSettings:
|
|
m_Enabled: 0
|
|
m_InitializeOnStartup: 1
|
|
m_TestMode: 0
|
|
m_IosGameId:
|
|
m_AndroidGameId:
|
|
m_GameIds: {}
|
|
m_GameId:
|
|
PerformanceReportingSettings:
|
|
m_Enabled: 0
|