Currently if the Unity integrator enables trace logging in Unity with Teak.Instance.Trace = true prior to Start(), the SDK will overwrite that setting with the native SDK setting in Start().
Off the top of my head I think we should make Unity's trace state a ternary -- "default", which will pull the value from the native SDK, or set to true or false explicitly by the integrator, in which case we should ignore the SDK setting (but possibly spit out a warning log if the Unity set value conflicts with the SDK set value).
Currently if the Unity integrator enables trace logging in Unity with
Teak.Instance.Trace = true
prior to Start(), the SDK will overwrite that setting with the native SDK setting in Start().Off the top of my head I think we should make Unity's trace state a ternary -- "default", which will pull the value from the native SDK, or set to true or false explicitly by the integrator, in which case we should ignore the SDK setting (but possibly spit out a warning log if the Unity set value conflicts with the SDK set value).