Open mkbey opened 6 months ago
Hi @mkbey, thanks for choosing Amplitude and put detailed description. It seems to be a bug and can be solved by a similar way of the PR in the possible solution section. I will keep you updated.
Hi @mkbey, thanks for choosing Amplitude and put detailed description. It seems to be a bug and can be solved by a similar way of the PR in the possible solution section. I will keep you updated.
Awesome thanks so much! Any timeline on a new version patch for this off the top? Would that roll up into another release or could it be deployed pretty quick here? Thanks again; rock on 🚀
@Mercy811 Any updates on timelines for processing? Any patch versions on the horizon here or?
Hi @mkbey, we are experiencing a high volume of customer issues. I just check the code where the warning comes from https://github.com/amplitude/Amplitude-Kotlin/blob/main/common-android/src/main/java/com/amplitude/common/android/AndroidContextProvider.kt#L236. I know this isn't ideal as already disableAdid()
and disableAppSetId()
. But It shouldn't block events from being sent to Amplitude. Also as you mentioned that your sister project works expected. Could you check their configurations and give us more context on why one is working while the other isn't. Thanks.
Expected Behavior
Expecting to be able to disable
adid
andappSetId
inTrackingOptions
when initializing Amplitude and expect events to show in my Production environmentCurrent Behavior
Google Play Services SDK not found for app set id!
apiKey
is accuratePossible Solution
AndroidContextProvider
forshouldFetchAppSetId
or something...looks like in that init block it always runsSteps to Reproduce
com.google.android.gms
Environment