Closed falconandy closed 1 year ago
Additional note: in Android-Kotlin default value for limitAdTrackingEnabled is true, in Amplitude-Android - false
Thanks for calling this out. I think this is because ADID usage is no longer recommended, but was at the time of Amplitude-Android's initial release. We probably kept the the legacy SDK as-is for backwards compatibility but changed it in the new SDK along with other breaking changes.
cc @qingzhuozhen
@justin-fiedler
Can you please try fixing the Identify tests some more pray I really want them to be reliable in CI so we can be confident in releases.
Fixed (removed global mocking from other tests). Some other tests are still unstable but re-run helps.
@Mercy811
Want to confirm that to disable tracking ADID, the usage remains the same but ADID is not fetched by the SDK.
yes, with trackingOptions.disableAdid()
the SDK shouldn't fetch ADID
:tada: This PR is included in version 1.9.2 :tada:
The release is available on:
v1.9.2
Your semantic-release bot :package::rocket:
Additional note: in Android-Kotlin default value for
limitAdTrackingEnabled
istrue
, in Amplitude-Android -false
Maybe if adid tracking is disabled
limitAdTrackingEnabled
should benull
.UPD: for some reason
IdentifyInterceptTest
fail in CI (work locally).Checklist