Google Play Services SDK not found for app set id!

[mkbey]

Expected Behavior

Expecting to be able to disable adid and appSetId in TrackingOptions when initializing Amplitude and expect events to show in my Production environment

Current Behavior

• I get this warning Google Play Services SDK not found for app set id!
• No events show up for my project. apiKey is accurate

Possible Solution

• Link to Flutter issues Google Play Services SDK not found for app set id!
• Link to PR for #125
• Believe like the PR above, we could add a param in AndroidContextProvider for shouldFetchAppSetId or something...looks like in that init block it always runs

Steps to Reproduce

• This is an MDM'd build and we have none of the Play Service dependencies: com.google.android.gms
• I've tried combinations of custom user/device ids but run into the same warning
• We have a sister project for lower environments (dev/test) and do not run into this warning...prod project has this issue though

private val trackingOptions = TrackingOptions().disableAdid().disableAppSetId()
private val amplitude = Amplitude(
        Configuration(
            apiKey = apiKey,
            context = context,
            flushIntervalMillis = 30000,
            flushEventsOnClose = true,
            flushQueueSize = 30,
            flushMaxRetries = 5,
            useBatch = true,
            identifyBatchIntervalMillis = 30000L,
            useAppSetIdForDeviceId = false,
            useAdvertisingIdForDeviceId = false,
            newDeviceIdPerInstall = false,
            trackingOptions = trackingOptions,
            locationListening = false,
        ),
    ).setUserId(customerUserId).setDeviceId(customDeviceId)

Environment

• Device: Tablet, API 29, Android 10.0

[Mercy811]

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.

[mkbey]

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 🚀

[mkbey]

@Mercy811 Any updates on timelines for processing? Any patch versions on the horizon here or?

[Mercy811]

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.