Admob UMP SDK with DataStore issue. [326681235]

Assigned

Bug

Status Update

No update yet.

Description

fa...@gmail.com

created issue #1

Feb 24, 2024 05:04PM

When using Admob UMP SDK with DataStore set with a migration that coincides with the xml used by UMP to store consent info, DataStore keeps deleting that xml file causing the consent form to keep showing up each time the user kills the app and relaunch it.

I modified the BannerExample project from Github and added the following code: MainActivity:

class MainActivity : AppCompatActivity() {

//.......

    override fun onCreate(savedInstanceState: Bundle?) {
	super.onCreate(savedInstanceState)

	CoroutineScope(Dispatchers.IO).launch {
	    val data = dataStore.data.first().toPreferences()
	}
    }

    companion object {

        private const val PREFS_FILE_NAME = "user_prefs"
        private val Context.dataStore by preferencesDataStore(
	   name = PREFS_FILE_NAME,
 	   produceMigrations = {
	     listOf(SharedPreferencesMigration(it, it.packageName + "_preferences"))
   	   }
        )
    }
}

Steps to produce the issue:

Replace TestDeviceHashedId inside GoogleMobileAdsConsentManager
Run the app and consent to the form
Kill the app from app drawer
Rerun the app and kill it again
Rerun the app last time you will be presented with the consent form

Github project: https://github.com/hiddeneyes02/BannerExample

One fix for this is to remove the migration, but that's not acceptable in some cases. The issue resides in UMP SDK using this xml file (package.name_preferences.xml) to store consent info, which is a common place for users to store their shared preferences, and this path is not configurable by the UMP.

Comments

vi...@google.com <vi...@google.com> #2Feb 25, 2024 07:49AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Which Android build are you using? (e.g. TQ3A.230705.001.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

fa...@gmail.com <fa...@gmail.com> #3Feb 29, 2024 04:58PM

Which Android build are you using? Android Studio Hedgehog | 2023.1.1 Patch 2 Build #AI-231.9392.1.2311.11330709, built on January 19, 2024 Runtime version: 17.0.7+0-b2043.56-10550314 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. Windows 11.0 GC: G1 Young Generation, G1 Old Generation Memory: 8192M Cores: 32 Registry: external.system.auto.import.disabled=true debugger.watches.in.variables=false debugger.new.tool.window.layout=true ide.text.editor.with.preview.show.floating.toolbar=false ide.experimental.ui=true

Which device did you use to reproduce this issue? Samsung F23-5G SM-E236B/DS and OPPO CPH1969 but it also happens on Emulator Pixel 3XL API25

Can you confirm if this issue is reproducible on a Pixel/Nexus device? I can't, but it also occures on emulator.

Bug report here (don't think it is relevant because no crash is happening): https://drive.google.com/file/d/1LubHT97o41f3R0TfhqmyMTbm1tBA1ZmU/view?usp=sharing

vi...@google.com <vi...@google.com> #4Mar 4, 2024 01:03AM

Comment has been deleted.

Message last modified on Mar 7, 2024 04:50AM

vi...@google.com <vi...@google.com> #5Mar 7, 2024 04:50AM

Status: Won't Fix (Infeasible)

Thank you for reporting this issue. The issue you have logged is related to Google Ads (AdMob). For Google Ads (AdMob) issue, please visit Google Mobile Ads SDK Technical Forum as indicated on the AdMob Support Resources page

fa...@gmail.com <fa...@gmail.com> #6Mar 7, 2024 07:35AM

I don't understand why you consider it as Admob issue but not DataStore issue. As always this is expected from you to not resolve this kind of issue, you are too busy for it.

Let's see what Admob thinks about it.

vi...@google.com <vi...@google.com> Mar 11, 2024 06:13PM

Status: Assigned (reopened)

vi...@google.com <vi...@google.com> #7Mar 12, 2024 03:47PM

As per the TCF V2 spec, the default shared preference shall be used to persist the consent strings, https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20CMP%20API%20v2.md#how-do-third-party-sdks-vendors-access-the-consent-information-in-app.

This has been standardized by the spec and all other SDKs or the publishers themselves should respect the same storage location to share the consent strings.

What's the motivation for the publishers to use DataStore?

fa...@gmail.com <fa...@gmail.com> #8Mar 12, 2024 04:13PM

Nobody is talking about publishers or any SDK using DataStore. We as a developers are allowed to use DataStore, but if we do it in the same manner showed in the example project, we keep losing consent info stored by UMP SDK in default shared preferences. To me it is a DataStore issue not providing non destructive migration.