User Messaging Platform (UMP) min Android version supported

[Gicci]

Requesting a consent form on a device with Android SDK version 19 results in an error 3 "Publisher misconfiguration: Android SDK version  is not supported" (note that the version is not printed).

Google Mobile Ads SDK requires apps to be on a minimum Android API level 19 to run, so I expect that also the UMP should have the same requirement.

As this seems to not be the case, which is the min Android SDK supported by the UMP?

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for reaching out to us.

After testing this using our sample app and with the minimum Android SDK version of 19, we did not encounter this error you described. For us to look into this further, kindly provide us the following information below privately:

• Sample App
• Steps to replicate
• SDK Version
• Screenshots of the error

You can provide the following details via reply privately to author option or directly provide it to the link below.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=5004Q00002nRmZmQAK&entry.80707362=00189640

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

This message is in relation to case "ref:_00D1U1174p._5004Q2nRmZm:ref"

Thanks,
 

Mobile Ads SDK Team

[Gicci]

Files sent.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for your response.

We checked your app in both version 19 and 33. However, can you confirm if we are expecting to have a consent popup upon app launch in both version 19 and 33? In addition to that, kindly confirm if the consent is not showing in version 19 because of the warning message, but was able to show in version 33? Can you also provide us with a screen recording of your replication so we can further check? Once provided and confirmed, we will further check this in our end, and will confirm.

[Gicci]

Hi,

sorry, I was imprecise in my first post: the issue presents itself when calling requestConsentInfoUpdate(), not when showing the consent popup. In the example app I provided I never trigger the popup show because the issue I am reporting happens before that step.

If you look at the logcat logs I attached (and that you can replicate with the provided source code) you can see that on the API 19 emulator there is:

UserMessagingPlatform    W  Publisher misconfiguration: Android SDK version  is not supported
UmpCmpGdpr               W  Error requesting consent info update: 3 Publisher misconfiguration: Android SDK version  is not supported

while on API 33 there is:

UmpCmpGdpr   D  Consent information received. Status: 2, Form available: true
UmpCmpGdpr   D  Requesting consent form

[...]

UmpCmpGdpr   D  Consent form received

These printouts are generated from this part of the provided code:

// request an update
consentInformation.requestConsentInfoUpdate(activity, params,
        () -> {
            // the consent information state was updated and we are now ready to check if a form is available
            if (Misc.DEBUG) Log.d(TAG, "Consent information received. Status: " + consentInformation.getConsentStatus() +
                    ", Form available: " + consentInformation.isConsentFormAvailable());

            // load the consent form
            loadConsentForm(() -> {
                // notify initialization
                onInit(UmpCmpGdpr.this);
            });
        },
        formError -> {
            // handle the error
            if (Misc.DEBUG) Log.w(TAG, "Error requesting consent info update: " +
                    formError.getErrorCode() + " " + formError.getMessage());

            // notify initialization
            onInit(UmpCmpGdpr.this);
        });

So on API 19 the error ConsentInformation.OnConsentInfoUpdateFailureListener callback is triggered.

I haven't checked if I am able or not to load the consent form on API 19 as, also in the sample code you provide at https://developers.google.com/admob/android/privacy#load-form, I am not supposed to continue loading a form if requestConsentInfoUpdate() fails.

https://developers.google.com/admob/android/privacy#load-form

https://developers.google.com/admob/android/privacy#load-form

[Mobile Ads SDK Forum Advisor]

Hello Gicci,

Thank you for clarifying.

However, upon attempting to reproduce this behavior using the sample app you provided, we were still unsuccessful. Would it be possible to provide us a screen recording when this message appears?

[Gicci]

Hi,

I just uploaded a screen recording of the test app in execution on the emulator on the provided link.

BR

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Thank you for your response.

Let us share the following details to the wider team to further check and confirm the min android version for UMP. Rest assured that one of our team will reach out to you.

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Can you set up your application to use a test device programmatically and see if this helps?

Thanks,
Nick

ref:_00D1U1174p._5004Q2nRmZm:ref

[Gicci]

Hi,

I configured the device as test device in the MobileAds SDK right at the beginning the  but the effect is the same.

BR

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Thank you for providing that information. What version of UMP SDK are you using? 

Thanks,
Justin

ref:_00D1U1174p._5004Q2nRmZm:ref

[Gicci]

As per the sample app I already provided, the one included with

com.google.android.gms:play-services-ads:22.2.0

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Thank you for that. The minimum Android SDK version supported by the UMP SDK 16. 

[Gicci]

And so, why it reports the error 3 "Publisher misconfiguration: Android SDK version  is not supported" on an API 19?

Could it be related to an old Google Play Services version on the device instead?

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Thank you for your question. That does look like an issue because that extra space in the log should be the SDK version but it is coming back as blank. I am also able to replicate this will your sample project using a Pixel 2 API 19. I will escalate this to the greater engineering to further investigate your case and will respond back here as soon as it is resolved. 

[Gicci]

Hi,

do you have any news on this issue?

Thanks.

[Mobile Ads SDK Forum Advisor]

Hi Gicci,

Thank you for following up. At this time the engineering team is still looking into your case and I will respond back here as soon as I have an update. Thank you for your patience.

[Ta-Dah Apps]

Just to add weight to this, we are also experiencing this issue so a fix would be appreciated.

[Gicci]

Any news on the min SDK version really supported?

The deadline is approaching and we need to decide how to handle this situation...

Thank you.

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your patience. I have heard back from the engineering team and the minimum SDK version is 21. This has been recently amended to our Android documentation as well. 

[izzy.ma...@gmail.com]

I am currently trying to implement the UMP SDK and testing it out I get an error code "4" and error message "web view timed out" when using a virtual device that has api 23 or less,  i've tested the exact same virtual device with api 24 and above and it works fine.  so my question is , is the new minimum api required 24 and the android docs just haven't been updated ? 

[Mobile Ads SDK Forum Advisor]

Hello,

The minimum API is 21. The "web view timed out" error is due to the the web view taking too long to load. This may happen on older versions due to the privacy message form loading being a heavy-task process. A recommendation is to manage your GDPR ad partners to only use the partners you need. 
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02nRmZm:ref" (ADR-00189640)

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               
 

 

[izzy.ma...@gmail.com]

How do I know which ad partners I need ? If i am only using admob without mediation does that mean I should only the default 1 selected (Google) or does mediation not have anything to do with number of ad partners ? and if i do decide to use mediation does that mean I should select whatever ad networks i have in my mediation stack to the list of ad partners to show ? will selecting all or selecting a small list of ad partners have any affect on ads shown or revenue ? 

Thank you 

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your questions. To help with your use case, we recommend you read the Manage GDPR ad partners Help Center article which will answer your questions.